debug-issue

Start with semantic search to find code related to the issue, then trace callers and callees to follow the call chain. Use flow retrieval to see full execution paths and change detection to check whether recent edits caused the problem.

Use the graph query tool with callers_of and callees_of on the suspected function. Checking both directions reveals the full context, from the entry point that triggers the code down to the operations it invokes.

Yes, the change detection tool identifies recent modifications in the codebase. Since recent changes are the most common source of new issues, correlating them with the affected flow usually pinpoints the culprit.

Always begin with get_minimal_context for your task before calling other graph tools, and use detail_level minimal on all calls. Only escalate to standard detail when minimal output is insufficient, targeting five or fewer tool calls.

Impact radius analysis shows which other files and flows are affected by a suspected file. Running it on candidate files helps you understand the blast radius of a bug and verify whether a fix might break dependent code.