Code-review-graph Debug Issue

Name: Debug Issue
Author: tirth8205

Systematically debug issues using graph-powered code navigation

install

source · Clone the upstream repo

git clone https://github.com/tirth8205/code-review-graph

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/tirth8205/code-review-graph "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/debug-issue" ~/.claude/skills/tirth8205-code-review-graph-debug-issue && rm -rf "$T"

manifest: skills/debug-issue/SKILL.md

source content

Debug Issue

Use the knowledge graph to systematically trace and debug issues.

Steps

Use
```
semantic_search_nodes
```
to find code related to the issue.
Use
```
query_graph
```
with
```
callers_of
```
and
```
callees_of
```
to trace call chains.
Use
```
get_flow
```
to see full execution paths through suspected areas.
Run
```
detect_changes
```
to check if recent changes caused the issue.
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.