tirth8205/code-review-graph

debug-issue

Systematically debug issues using graph-powered code navigation

First seen Jul 17, 2026

Installation

$ npx skills add tirth8205/code-review-graph --skill debug-issue

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tirth8205/code-review-graph.

npx skills add tirth8205/code-review-graph

Browse all from tirth8205/code-review-graph

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 31.3K
License LICENSE
Default branch main
Open issues 88
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,226 B
  • docs SUMMARY.md 1,199 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 955 installs

SKILL.md

Debug Issue

Use the knowledge graph to systematically trace and debug issues.

Steps

  1. Use semanticsearchnodes_tool to find code related to the issue.
  2. Use querygraphtool with callersof and calleesof to trace call chains.
  3. Use getflowtool to see full execution paths through suspected areas.
  4. Run detectchangestool to check if recent changes caused the issue.
  5. Use getimpactradius_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

  • Start with getminimalcontext_tool(task="<your task>") before other graph tools.
  • 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.
  • Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.