1.1 KiB
1.1 KiB
| name | description |
|---|---|
| Debug Issue | Systematically debug issues using graph-powered code navigation |
Debug Issue
Use the knowledge graph to systematically trace and debug issues.
Steps
- Use
semantic_search_nodesto find code related to the issue. - Use
query_graphwithcallers_ofandcallees_ofto trace call chains. - Use
get_flowto see full execution paths through suspected areas. - Run
detect_changesto check if recent changes caused the issue. - Use
get_impact_radiuson suspected files to see what else is affected.
Tips
- Check both callers and callees to understand the full context.
- Look at affected flows to find the entry point that triggers the bug.
- Recent changes are the most common source of new issues.
Token Efficiency Rules
- ALWAYS start with
get_minimal_context(task="<your task>")before any other graph tool. - Use
detail_level="minimal"on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.