| name | debug-issue |
| description | Systematically debug issues using graph-powered code navigation, recent-change detection, affected flows, and targeted verification. |
Debug Issue
Use the graph to trace suspected code paths and recent changes before editing.
Core Rules
- Start with
get_minimal_context_tool(task="<bug or symptom>").
- Use graph navigation to find suspects, then read source files directly.
- Prefer one hypothesis at a time with a targeted verification command.
- If graph tools are unavailable, fall back to
rg, tests, logs, and runtime probes.
Workflow
- Search related symbols with
semantic_search_nodes_tool().
- Trace callers and callees with
query_graph_tool(pattern="callers_of"|"callees_of").
- Check entry paths with
get_affected_flows_tool() or get_flow_tool().
- Run
detect_changes_tool() when the bug may be regression-related.
- Use
get_impact_radius_tool() before patching suspected shared code.
- Patch only the smallest confirmed cause.
- Verify with focused tests, lint, type-check, or a targeted runtime probe.
Output
Lead with:
- root cause
- changed files
- verification run
- remaining risk or missing coverage
