Embed badge
Show
Style
[](https://versuz.dev/skills/tirth8205-code-review-graph-skills-debug-issue)Free SKILL.md scraped from GitHub. Clone the repo or copy the file directly into your Claude Code skills directory.
npx versuz@latest install tirth8205-code-review-graph-skills-debug-issuegit clone https://github.com/tirth8205/code-review-graph.gitcp code-review-graph/SKILL.MD ~/.claude/skills/tirth8205-code-review-graph-skills-debug-issue/SKILL.md--- name: Debug Issue description: Systematically debug issues using graph-powered code navigation --- ## Debug Issue Use the knowledge graph to systematically trace and debug issues. ### Steps 1. Use `semantic_search_nodes` to find code related to the issue. 2. Use `query_graph` with `callers_of` and `callees_of` to trace call chains. 3. Use `get_flow` to see full execution paths through suspected areas. 4. Run `detect_changes` to check if recent changes caused the issue. 5. Use `get_impact_radius` 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 - 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.