debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, t
By jeffallan · 4,393 installs
npx skills add jeffallan/claude-skills --skill debugging-wizard
Source repository · Upstream listing
Debugging Wizard
Expert debugger applying systematic methodology to isolate and resolve issues in any codebase.
Core Workflow
1. Reproduce Establish consistent reproduction steps
2. Isolate Narrow down to smallest failing case
3. Hypothesize and test Form testable theories, verify/disprove each one
4. Fix Implement and verify solution
5. Prevent Add tests/safeguards against regression
Reference Guide
Load detailed guidance based on context:
<! Systematic Debugging row adapted from obra/superpowers by Jesse Vincent (@obra), MIT License
Topic Reference Load When
Debugging Tools references/debugging tools.md Setting up debuggers by language
Common Patterns references/common patterns.md Recognizing bug patterns
Strategies references/strategies.md Binary search, git bisect, time travel
Quick Fixes references/quick fixes.md Common error solutions
Systematic Debugging references/systematic debugging.md Complex bugs, multiple failed fixes, root cause analysis
Constraints
MUST DO
Reproduce the issue first
Gather complete error messages and stack traces
Test one hypothesis at a time
Document findings for future reference
Add regression tests after fixing
Remove all debug code before committing
MUST NOT DO
Guess without testing
Make multiple changes at once
Skip reproduction steps
Assume you know the cause
Debug in production without safeguards
Leave console.log/debugger statements in code
Common Debugging Commands
Python (pdb)
JavaScript (Node.js)
Git bisect (regression hunting)
Go (delve)
Output Templates
When debugging, provide:
1. Root Cause : What specifically caused the issue
2. Evidence : Stack trace, logs, or test that proves it
3. Fix : Code change that resolves it
4. Prevention : Test or safeguard to prevent recurrence
[Documentation](https://jeffallan.github.io/claude skills/skills/quality/debugging wizard/)