メニュー
Blast radius before a change — everything a node affects (forward) or that depends on it (backward), ranked and located, with likely-dead code flagged. Also the one-hop view of direct connections.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Start from a failure, not a filename — turn a stacktrace, failing test, or diff into the exact code that matters, then read it. Use when you have an error and need to know where to look.
Locate where a feature or symbol lives — match nodes by name, or pull the related cluster from a seed via spreading activation. Use to scope before reading.
Set up or rebuild the structural graph for a repo — on first use, after a big refactor, or to wire repo-graph into a project permanently.
Get oriented in a codebase before reading files — repo shape, entry points, where the graph is blind, and the full structural map. Use at the start of any task in an unfamiliar or large repo.
Follow the code across boundaries — a feature end-to-end, or the shortest path between two nodes (e.g. a frontend action to its backend handler). Links across the stack in one call instead of grepping both sides.
| name | repo-graph-impact |
| description | Blast radius before a change — everything a node affects (forward) or that depends on it (backward), ranked and located, with likely-dead code flagged. Also the one-hop view of direct connections. |
Know what a change touches before you make it.
impact with nodes=<name>. direction=forward (what it affects, the default sense) / backward (what it depends on / who uses it) / both; depth is 1–10. Pass several comma-separated nodes (e.g. every symbol in a diff) for the unified blast radius in one call. Each row shows a via <reason> edge label and a ⊘ marker when the engine finds the node unreachable from any entry point — likely dead code. Add live_only=true to drop those.impact at depth=1 with direction=both — direct callers and callees one hop out (this replaces the old neighbours tool).⊘.