Birdview

中文

Show the system on an evidence-linked architecture map and highlight the modules AI plans to change before editing.

Activation

Project off disables the foundation and map workflow unless explicitly requested for the current task. Installed project foundation rules remain applicable in on-demand even without skill activation; their canonical managed text is foundation.txt. For project setup, disabling or removal of managed rules, follow modes.md; do not start mapping merely to configure rules.

Birdview defaults to on-demand: activate when the user selects the skill, names Birdview, requests an architecture/constraint/change map, or requests architecture improvement through the review route below. Ordinary coding, small fixes and feature planning do not activate it by default. If the project host instruction file explicitly configures auto, activate before every code-changing task, including small edits, and planning that explicitly analyzes affected modules. Honor existing auto settings; setup preserves them. Honor off unless explicitly invoked for this task. Merely discussing the skill does not request a map. When active for authorized coding, reuse/update the map and declare affected modules before editing.

In Codex, use /skills to select Birdview or mention $birdview. For the separate environment audit, use $birdview-compatibility; it does not activate mapping. Claude Code exposes these installed skills as /birdview and /birdview-compatibility. Other hosts use their skill selector or an explicit request; do not assume they implement the same slash command. Invocation applies to the current task, not all future edits.