Menú
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.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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.
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-debug |
| description | 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. |
Paste the error, get the code. The on-ramp when something's broken — instead of grepping file names out of a traceback and opening each one.
path::test_name), or a diff / list of changed files.find with query=<the raw stacktrace / test id / unified diff>. It sniffs the shape (or pass kind=stacktrace|test|diff), resolves the frames/symbols/paths to nodes, then ranks the surrounding subgraph by relevance (Personalized PageRank). Every row carries path:line.read with node=<top result> to pull that node's exact source, sliced from its file by the graph's line span — no grep, no scrolling. Add context_lines=N for padding around it.impact on the node for blast radius (it takes several comma-separated nodes — feed it the whole changed set) — direction=both at depth=1 for direct callers/callees.find only resolves frames that actually exist in the graph — if it returns nothing, the signal's paths/symbols don't match this repo; fall back to find with a plain keyword.