# Birdview

Show evidence-linked architecture, constraints and change scope, or review architecture...

- Repository: https://github.com/Qiuner/birdview (668 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-09
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Qiuner/birdview --skill birdview -g -a claude-code -y`
Codex: `npx skills add Qiuner/birdview --skill birdview -g -a codex -y`
Cursor: `npx skills add Qiuner/birdview --skill birdview -g -a cursor -y`
Gemini CLI: `npx skills add Qiuner/birdview --skill birdview -g -a gemini-cli -y`

## Description

Show evidence-linked architecture, constraints and change scope, or review architecture improvement opportunities. Use for Birdview/map requests or requests to optimize architecture, review module boundaries or 优化架构. Also activate before coding when the project explicitly configures Birdview auto mode. Ordinary coding does not activate Birdview without that opt-in.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Birdview

[中文](SKILL.zh.md)

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](references/foundation.txt). For project setup, disabling or removal of managed rules, follow [modes.md](references/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.

The rest: https://github.com/Qiuner/birdview/blob/HEAD//SKILL.md