Debug Issue Use the knowledge graph to systematically trace and debug issues. Steps 1. Use semantic search nodes tool to find code related to the issue. 2. Use query graph tool with callers of and callees of to trace call chains. 3. Use get flow tool to see full execution paths through suspected areas. 4. Run detect changes tool to check if recent changes caused the issue. 5. Use get impact radius tool on 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 Start with get minimal context tool(task="<your task ") before other graph tools. 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. Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.

debug-issue