braydio/CUSTODIAN / .claude/skills/debug-issue
debug-issue
UnverifiedSystematically debug issues using graph-powered code navigation
Debug Issue
Use the knowledge graph to systematically trace and debug issues.
Steps
- Use
semantic_search_nodes_toolto find code related to the issue. - Use
query_graph_toolwithcallers_ofandcallees_ofto trace call chains. - Use
get_flowto see full execution paths through suspected areas. - Run
detect_changes_toolto check if recent changes caused the issue. - Use
get_impact_radius_toolon 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
- In the persistent coordination checkout, start with
get_minimal_context(task="<your task>")when the graph is ready. - In a linked/ephemeral worktree, do not cold-build a graph merely because the first call reports
missing_graph,not_ready, empty/unmapped, or stale coverage. If baseline structural context is useful, point CRG at the persistent coordination root; then verify every implementation/review fact against the current worktree. - If the graph is unusable after one cheap attempt, immediately use targeted symbol/path reads. Current worktree files and
git diffare authoritative for branch-local changes. - When the task packet provides a bounded
## Context Pack, generate it once from the claimed worktree withscripts/ai/pack-context.sh task ...and use it instead of broad file dumping. - Use
detail_level="minimal"on graph calls. Escalate only when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 graph calls and ≤800 graph-output tokens.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |