菜单
Change risk analysis — detect blast radius, risk score, and breaking changes from git diffs. Use before any PR or merge. Triggers on "review PR", "check impact", "blast radius", "what breaks", "safe to merge".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Auto-configure AGENTS.md and brain/ knowledge docs for a new project. Use when setting up Brain Bootstrap in a new repository. Discovers the codebase, fills in templates, and writes project-specific configuration.
Use before any new feature, component, or behavioral change — when you need to explore requirements and design before writing code. Hard gate — no code until design is approved.
Build the project and verify it compiles cleanly. Use after making changes to confirm nothing is broken before running tests. Reads the build command from brain/build.md.
Activate safety mode — review every destructive command before running. Use before working on production infrastructure, migration scripts, or any task where a typo could be catastrophic.
Generate a user-facing changelog from git commits — categorize, filter noise, translate to user language. Pass a tag or date as argument (e.g. "$changelog v1.0.0" or "$changelog 2026-01-01").
Save session state before context gets full or before ending. Writes current task state, branch, and loaded docs to brain/tasks/todo.md so the next session can resume cleanly.
| name | code-review-graph |
| description | Change risk analysis — detect blast radius, risk score, and breaking changes from git diffs. Use before any PR or merge. Triggers on "review PR", "check impact", "blast radius", "what breaks", "safe to merge". |
Structural change safety gate. Builds an AST graph from source code, then on any diff computes:
| Question | Tool |
|---|---|
| Is this change safe to ship? | detect_changes_tool(base_branch="main") |
| Build/rebuild the graph | build_graph_tool(repo_path=".") |
| Graph status + stats | get_graph_info_tool |
| What changed vs main? | get_diff_tool(base_branch="main") |
| Node details | get_node_tool(node_id="<id>") |
| Node neighbors | get_neighbors_tool(node_id="<id>", depth=2) |
| Find by name | search_nodes_tool(query="AuthService") |
| Community structure | get_communities_tool |
| Critical path | get_critical_path_tool(source="<id>", target="<id>") |
| Dependency chain | get_dependency_chain_tool(node_id="<id>") |
build_graph_tool(repo_path=".") — first run only (or after major refactor)detect_changes_tool(base_branch="main") — risk score + blast radiusget_dependency_chain_tool on the highest-risk nodeget_neighbors_tool| Score | Meaning | Action |
|---|---|---|
| 0–25 | Low risk | Review and ship |
| 26–50 | Moderate | Verify blast radius manually |
| 51–75 | High | Write tests for affected nodes |
| 76–100 | Critical | Full review + stakeholder sign-off |
First build: build_graph_tool(repo_path=".") — ~6s for 500 files, ~30s for large repos.
After major refactor: build_graph_tool(repo_path=".", force_rebuild=True).
Config in .codex/config.toml:
[mcp_servers.code-review-graph]
command = "uvx"
args = ["code-review-graph@latest"]
build_graph_tool before first usepip install uv or brew install uv)build_graph_tool(force_rebuild=True) if graph seems stale