Gauntlith

debug-issue

Unclaimed, from tirth8205

Systematically debug issues using graph-powered code navigation

Skill

Launcher coming soon
Without the launcher
git clone https://github.com/tirth8205/code-review-graph.git
cd code-review-graph
git checkout e7f2fb2a8ef6f7f892c2de3c7bf6ca6a453aa79e

Then copy code-review-graph/skills/debug-issue into your app's skills folder, for example .claude/skills/debug-issue.

No known issues found32.7k starse7f2fb2a8ef6 · e7f2fb2 · pinned 12 Nov 2026
Permanent link

README at commit e7f2fb2 · shown without scripts

name: debug-issue description: Systematically debug issues using graph-powered code navigation

Debug Issue

Trace a bug through the knowledge graph before reading source.

Steps

  1. Call semantic_search_nodes_tool to find code related to the issue.
  2. Call query_graph_tool with callers_of and callees_of to trace the call chain in both directions.
  3. Call get_flow_tool for the execution path that reaches the suspect code. Its entry point is where the bug is triggered.
  4. Call detect_changes_tool to check whether a recent change caused the issue.
  5. Call get_impact_radius_tool on the suspect files to see what a fix would affect.

Token Efficiency Rules

  • Call get_minimal_context_tool(task="<your task>") before any other graph tool.
  • Pass detail_level="minimal" wherever a tool accepts it. Use "standard" only when minimal is not enough.
  • Prefer a targeted query_graph_tool call over a broad listing call.
  • Budget: about five tool calls and 800 tokens of graph output per task.
  • Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.