build-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
@tirth8205Install SkillCode Review
Skill
/debug-issue
Systematically debug issues using graph-powered code navigation
Claude Code
$ npx -y skills add tirth8205/code-review-graph --skill debug-issue --agent claude-code
Codex
$ npx skills add tirth8205/code-review-graph --skill debug-issue -a codex -y
Cursor
$ npx skills add tirth8205/code-review-graph --skill debug-issue -a cursor -y
Gemini CLI
$ npx skills add tirth8205/code-review-graph --skill debug-issue -a gemini-cli -y
GitHub Copilot
$ npx skills add tirth8205/code-review-graph --skill debug-issue -a github-copilot -y
OpenCode
$ npx skills add tirth8205/code-review-graph --skill debug-issue -a opencode -y
Windsurf
$ npx skills add tirth8205/code-review-graph --skill debug-issue -a windsurf -y
SKILL.md
debug-issue.SKILL.mdname: 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.
Ships withcode-review-graph
Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.
33k7 skills1 MCP
Stars on GitHub
Momentum
- stars in total
- 32.5k
Other skills on code-review-graph.
@tirth8205Install Skillexplore-codebase
Navigate and understand codebase structure using the knowledge graph
@tirth8205Install Skillreview-changes
Perform a structured code review using change detection and impact
@tirth8205Install Skillreview-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
@tirth8205Install Skillreview-pr
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius…
@tirth8205Install SkillMore skills from other plugins.
open-code-review
Performs AI-powered code review on Git changes using the `ocr` CLI from alibaba/open-code-review. Use when the user asks to…
@alibabaInstall Skilladdressing-pr-review-c…
Address all valid review comments on a PR for the current branch in the streamlit/streamlit repo. Covers both inline review…
@streamlitInstall Skillhunk-extensions
Maps the `hunkdiff/extension` authoring surface for Hunk, the terminal diff viewer — hiding or reordering reviewed files, docked…
@modem-devInstall Skill
Questions about debug-issue.
- Which coding agents can use debug-issue?
- debug-issue installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.