Debug issue
Skill cristianorj22/arthus-harness/plugins/mcp-code-review-graph/claude/skills/debug-issue
Opinionated Claude Code scaffolder — agents, skills, hooks, slash commands. Like create-t3-app, but for your .claude/. Install months of Claude Code discipline in 30 seconds.
npx -y skills add cristianorj22/arthus-harness --skill debug-issueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Systematically debug issues using graph-powered code navigation (code-review-graph MCP). Companion to the `debugger` agent — graph navigation gives breadth, agent gives depth.
SKILL.md
1.4 KB, as published. Nobody here has run it
Debug Issue (graph-powered)
Use the knowledge graph to systematically trace and debug issues.
Steps
- Use
semantic_search_nodesto find code related to the issue. - Use
query_graphwithcallers_ofandcallees_ofto trace call chains. - Use
get_flowto see full execution paths through suspected areas. - Run
detect_changesto check if recent changes caused the issue. - Use
get_impact_radiuson 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
- ALWAYS start with
get_minimal_context(task="<your task>")before any other graph tool. - 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.
Cross-link
- Pairs with the
debuggeragent (4-phase systematic debugging). Agent does the thinking (5 Whys, root cause); this skill does the navigation (callers, flows, impact).