Debug
Debug errors with systematic 6-step protocol. Paste error message or describe the bug.From its SKILL.md
npx -y skills add RhythmMittal19/claude-config --skill debugAssembled 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.
SKILL.md
1.4 KB, 283 tokens by cl100k_base, as published. Nobody here has run it
Error/Bug Report
$ARGUMENTS
Current State
!git branch --show-current 2>/dev/null
!git diff --stat 2>/dev/null | head -10
Debugging Protocol — Follow these steps IN ORDER:
Step 1: Reproduce
- Identify the exact trigger for the error
- Note the full stack trace and error message
Step 2: Isolate
- Use subagents to search for relevant code: the error source, related modules, tests
- Identify the smallest possible scope where the bug lives
Step 3: Hypothesize
- Form 2-3 hypotheses about root cause
- List evidence for/against each
Step 4: Verify
- Test the most likely hypothesis FIRST
- Use targeted reads, not full-file scans
- Check git blame if the code worked before: when did it break?
Step 5: Fix
- Make the minimal change that fixes the root cause (not symptoms)
- NEVER change code you don't understand hoping it fixes things
Step 6: Confirm
- Run tests to verify the fix
- Check for regressions in related functionality
- Explain what caused the bug and why the fix works
IMPORTANT: If you've tried the same approach twice and it didn't work, STOP and try a fundamentally different strategy.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.