Debug Issue Trace a bug through the knowledge graph before reading source. Steps 1. Call semantic search nodes tool to find code related to the issue. 2. Call query graph tool with callers of and callees of to trace the call chain in both directions. 3. Call get flow tool for the execution path that reaches the suspect code. Its entry point is where the bug is triggered. 4. Call detect changes tool to check whether a recent change caused the issue. 5. Call get impact radius tool on the suspect files to see what a fix would affect. Token Efficiency Rules Call get minimal context tool(task="<your task ") before any other graph tool. Pass detail level="minimal" wherever a tool accepts it. Use "standard" only when minimal is not enough. Prefer a targeted query graph tool call over a broad listing call. Budget: about five tool calls and 800 tokens of graph output per task. Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.

debug-issue