debug-issue
Systematically debug issues using graph-powered code navigation
Install
npx skills add https://github.com/tirth8205/code-review-graph --skill debug-issueSKILL.md
Debug Issue
Trace a bug through the knowledge graph before reading source.
Steps
- Call
semantic_search_nodes_toolto find code related to the issue. - Call
query_graph_toolwithcallers_ofandcallees_ofto trace the call chain in both directions. - Call
get_flow_toolfor the execution path that reaches the suspect code. Its entry point is where the bug is triggered. - Call
detect_changes_toolto check whether a recent change caused the issue. - Call
get_impact_radius_toolon 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_toolcall 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.
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".