---
name: Debug Issue
slug: debug-issue
category: Quality
description: Debug Issue traces bugs through a code knowledge graph so developers can isolate root causes faster. Use it when investigating regressions, analyzing call paths, or checking recent changes.
github: "https://github.com/tirth8205/code-review-graph/tree/main/skills/debug-issue"
language: Python
stars: 30048
forks: 2760
install: "npx degit https://github.com/tirth8205/code-review-graph/tree/main/skills/debug-issue ~/.claude/skills/debug-issue"
installs_to: ~/.claude/skills/debug-issue
source_path: skills/debug-issue/SKILL.md
collection_size: 7
category_size: 1354
collection_url: "https://dirskills.com/collections/tirth8205/code-review-graph"
added: 2026-08-14T07:11:47.698Z
last_synced: 2026-08-14T07:11:47.698Z
canonical_url: "https://dirskills.com/skills/debug-issue"
---

# Debug Issue

Debug Issue traces bugs through a code knowledge graph so developers can isolate root causes faster. Use it when investigating regressions, analyzing call paths, or checking recent changes.

**Install:**

```bash
npx degit https://github.com/tirth8205/code-review-graph/tree/main/skills/debug-issue ~/.claude/skills/debug-issue
```

## README

## 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` 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
- 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.