New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Graph-Based Bug Tracing

by tirth8205 in tirth8205/code-review-graph

Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

MITAuto-check passedDevelopment

Install Graph-Based Bug Tracing

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tirth8205/code-review-graph debug-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tirth8205/code-review-graph.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/debug-issue .claude/skills/debug-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
debug-issue
GitHub stars
32k
Used in
1 other repo
Token cost
~287 tokens
SKILL.md length
153 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

  • Works in 5 steps: Call semantic_search_nodes_tool to find… → Call query_graph_tool with callers_of… → Call get_flow_tool for the execution… → …
  • Tracing where a bug is triggered across a call chain
  • SKILL.md covers Debug Issue and Token Efficiency Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill runs five graph tools in order: a semantic search for code related to the issue, a graph query for callers and callees in both directions, a flow lookup for the execution path whose entry point is where the bug is triggered, a change detector to see whether a recent change caused it, and an impact-radius check on suspect files to see what a fix would affect.

Token efficiency rules ask for the minimal-context tool first, minimal detail levels wherever accepted, targeted queries over broad listings, and a budget of about five tool calls and 800 tokens of graph output per task. The graph narrows the search but does not replace reading: the implementation and its tests are read before any change.

When your agent uses it

  • Tracing where a bug is triggered across a call chain
  • Checking whether a recent change caused a regression
  • Estimating what a fix will affect before editing

Example prompts

  • “Debug why checkout totals are wrong; start from the graph, not the files.”
  • “Trace the callers of validate_token and tell me which flow reaches it.”

Requirements

  • The code-review-graph tools available through MCP for the repository

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit 6b12d11. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Graph-Based Bug Tracing loads about 287 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 153 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~287

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tirth8205/code-review-graph at commit 6b12d11, republished under its MIT licence (© tirth8205). 153 words, ~287 tokens.

Download SKILL.mdSave it as .claude/skills/debug-issue/SKILL.md (or your agent's skills folder).
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.

© tirth8205, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/debug-issue of tirth8205/code-review-graph.

Open the folder on GitHubat commit 6b12d11

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in tirth8205/code-review-graph, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Graph-Based Bug Tracing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Graph-Based Bug Tracing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Graph-Based Bug Tracing this skilltirth8205/code-review-graph32k1 repos~287Automated safety check: PassMIT
Octocode Code Researchbgauryy/octocode946—~1.5kAutomated safety check: PassMIT
Debugagentic-community/mcp-gateway-registry962—~1.8kAutomated safety check: NotesApache-2.0
Broken UI Debuggerreticlehq/reticle1.2k—~1.3kAutomated safety check: PassApache-2.0
Sentry Fix Issuesgetsentry/sentry-for-ai2683 repos~1.9kAutomated safety check: PassApache-2.0
Flowstudio Power Automate Debuggithub/awesome-copilot40k2 repos~5kAutomated safety check: PassMIT

Similar skills

  • Octocode Code Research

    bgauryy/octocode

    Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.

    946 GitHub stars~1.5k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Debug

    agentic-community/mcp-gateway-registry

    Debug issues in the MCP Gateway Registry using first-principles thinking.

    962 GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Broken UI Debugger

    reticlehq/reticle

    Finds why a running web app misbehaves when the console is empty and the code looks fine, by reading the click, request, store and console together.

    1.2k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Sentry Fix Issues

    getsentry/sentry-for-ai

    Official

    Find and fix issues from Sentry using MCP. An agent skill from getsentry/sentry-for-ai.

    268 GitHub starsUsed in 3 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Flowstudio Power Automate Debug

    github/awesome-copilot

    Official

    Debug failing Power Automate cloud flows using the FlowStudio MCP server.

    40k GitHub starsUsed in 2 repos~5k tokens
    DevelopmentAuto-check passed

  • Flowstudio Power Automate Monitoring

    github/awesome-copilot

    Official

    Pro+ subscription required. An agent skill from github/awesome-copilot.

    40k GitHub starsUsed in 2 repos~3.3k tokens
    DevelopmentAuto-check passed

More from tirth8205/code-review-graph

  • Knowledge Graph PR Review

    tirth8205/code-review-graph

    Reviews a pull request or branch diff with a code knowledge graph and produces a structured review that includes blast-radius analysis.

    32k GitHub stars~452 tokensUpdated today
    Auto-check passed

  • Explore Codebase with Graph

    tirth8205/code-review-graph

    Navigates a codebase through the code-review-graph MCP tools: architecture overview, symbol search, caller and callee tracing, flows and oversized functions.

    32k GitHub starsUsed in 1 repo~335 tokens
    Auto-check passed

  • Graph-Guided Safe Refactoring

    tirth8205/code-review-graph

    Plans a refactor from a code dependency graph, previews renames before applying them and checks that the final impact matches the plan.

    32k GitHub starsUsed in 1 repo~332 tokens
    Auto-check passed

  • Graph-Based Change Review

    tirth8205/code-review-graph

    Reviews a change set using a code knowledge graph for risk scores, blast radius and test gaps, and ends with a merge recommendation.

    32k GitHub starsUsed in 1 repo~331 tokens
    Auto-check passed

  • Code Review Graph Builder

    tirth8205/code-review-graph

    Builds or incrementally updates the code-review knowledge graph for a repository and reports whether the build succeeded, partly or failed.

    32k GitHub stars~295 tokensUpdated today
    Auto-check passed

  • Review Delta

    tirth8205/code-review-graph

    Reviews only the code changed since the last commit, using a code-graph MCP server to find risk-scored changes, test gaps and the blast radius, then writes a short report.

    32k GitHub stars~325 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Graph-Based Bug Tracing

What does Graph-Based Bug Tracing do?

Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget. The skill runs five graph tools in order: a semantic search for code related to the issue, a graph query for callers and callees in both directions, a flow lookup for the execution path whose entry point is where the bug is triggered, a change detector to see whether a recent change caused it, and an impact-radius check on suspect files to see what a fix would affect.

When should I use Graph-Based Bug Tracing?

Graph-Based Bug Tracing fits situations like: tracing where a bug is triggered across a call chain; checking whether a recent change caused a regression; estimating what a fix will affect before editing.

How do I install Graph-Based Bug Tracing in Claude Code?

Run `npx skills add tirth8205/code-review-graph --skill debug-issue -a claude-code`. Or copy the skill folder (skills/debug-issue in tirth8205/code-review-graph) into .claude/skills/debug-issue in your project. Claude Code loads it when a task matches its description.

How do I install Graph-Based Bug Tracing in Codex?

Run `npx skills add tirth8205/code-review-graph --skill debug-issue -a codex`. Or copy the skill folder (skills/debug-issue in tirth8205/code-review-graph) into .agents/skills/debug-issue in your project. Codex loads it when a task matches its description.

Can I use Graph-Based Bug Tracing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tirth8205/code-review-graph --skill debug-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-issue, .gemini/skills/debug-issue, .github/skills/debug-issue and .opencode/skills/debug-issue in your project.

What does Graph-Based Bug Tracing need to run?

SKILL.md names no scripts, command-line tools or credentials: Graph-Based Bug Tracing is instructions for the agent only. Our summary lists: The code-review-graph tools available through MCP for the repository.

Does Graph-Based Bug Tracing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Graph-Based Bug Tracing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Graph-Based Bug Tracing use?

Graph-Based Bug Tracing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Graph-Based Bug Tracing use?

About 287 tokens (SKILL.md is roughly 1.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Graph-Based Bug Tracing?

Skills that share tags, products or a category with Graph-Based Bug Tracing: Octocode Code Research (bgauryy/octocode, 946 stars), Debug (agentic-community/mcp-gateway-registry, 962 stars), Broken UI Debugger (reticlehq/reticle, 1.2k stars) and Sentry Fix Issues (getsentry/sentry-for-ai, 268 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Graph-Based Bug Tracing?

tirth8205 (a GitHub user) maintains it in tirth8205/code-review-graph, which has 31,943 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.

Source: tirth8205/code-review-graph on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.