Debugging Wizard
FreeSystematic debugging tool for isolating and resolving issues.
Free · Opens the source repo
What Debugging Wizard does
Debugging Wizard is a specialized tool designed to assist developers in systematically identifying and resolving bugs within their codebases. By following a structured methodology, it helps users reproduce errors, isolate the root cause, and implement effective fixes. This skill is particularly useful for developers who frequently encounter complex bugs and need a reliable framework to guide their debugging process.
The core workflow of Debugging Wizard is built around five key steps: Reproduce, Isolate, Hypothesize and Test, Fix, and Prevent. Users start by establishing consistent reproduction steps for the issue at hand, which is crucial for understanding the problem. Next, they narrow down the issue to the smallest failing case, allowing for targeted analysis. The skill encourages forming testable hypotheses and verifying each one, ensuring that solutions are based on evidence rather than assumptions. Finally, once a fix is implemented, it emphasizes the importance of adding regression tests to prevent future occurrences of the same issue.
In addition to the core workflow, Debugging Wizard provides a reference guide that includes detailed information on debugging tools, common patterns, strategies for effective debugging, quick fixes for common errors, and systematic debugging techniques. This comprehensive set of resources equips developers with the knowledge they need to tackle a wide range of debugging scenarios, from simple errors to more complex issues that require thorough investigation.
Debugging Wizard is ideal for developers looking to improve their debugging skills and streamline their workflow. It is particularly beneficial for those working in teams where consistent debugging practices can enhance collaboration and reduce the time spent on troubleshooting. By providing a clear framework and valuable resources, this skill empowers developers to tackle bugs more efficiently and effectively.
When to use it
Use this skill when you need to investigate errors, analyze stack traces, or perform root cause analysis in your code.
When not to use it
Avoid using this skill for simple issues that can be resolved quickly without a systematic approach, or in production environments without proper safeguards.
What you can build with it
Investigating Application Crashes
When your application crashes unexpectedly, use Debugging Wizard to reproduce the issue and analyze stack traces for root cause identification.
Analyzing Log Files
Utilize Debugging Wizard to correlate log entries and pinpoint failure points in your application, streamlining the troubleshooting process.
Performing Regression Testing
After fixing a bug, apply Debugging Wizard's methodology to add regression tests, ensuring that the issue does not recur in future updates.
How to install Debugging Wizard
View source1. Install with the skills CLI
npx skills add jeffallan/claude-skills/debugging-wizard --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by jeffallanDebugging Wizard
Expert debugger applying systematic methodology to isolate and resolve issues in any codebase.
Core Workflow
- Reproduce - Establish consistent reproduction steps
- Isolate - Narrow down to smallest failing case
- Hypothesize and test - Form testable theories, verify/disprove each one
- Fix - Implement and verify solution
- 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)
python -m pdb script.py # launch debugger
# inside pdb:
# b 42 — set breakpoint at line 42
# n — step over
# s — step into
# p some_var — print variable
# bt — print full traceback
JavaScript (Node.js)
node --inspect-brk script.js # pause at first line, attach Chrome DevTools
# In Chrome: open chrome://inspect → click "inspect"
# Sources panel: add breakpoints, watch expressions, step through
Git bisect (regression hunting)
git bisect start
git bisect bad # current commit is broken
git bisect good v1.2.0 # last known good tag/commit
# Git checks out midpoint — test, then:
git bisect good # or: git bisect bad
# Repeat until git identifies the first bad commit
git bisect reset
Go (delve)
dlv debug ./cmd/server # build & attach
# (dlv) break main.go:55
# (dlv) continue
# (dlv) print myVar
Output Templates
When debugging, provide:
- Root Cause: What specifically caused the issue
- Evidence: Stack trace, logs, or test that proves it
- Fix: Code change that resolves it
- Prevention: Test or safeguard to prevent recurrence
Frequently asked questions about Debugging Wizard
Similar skills
Agent Host Debug Logs
Analyze Agent Host debug logs for deeper insights.
Code OSS Dev - Launch + Debug
Launch and debug Code OSS with isolated profiles.
Phoenix CLI
Debug LLM applications with structured analysis tools.
Power Automate Debugging
Diagnose and fix Power Automate flow errors effectively.
Arize Trace
Inspect and export traces for LLM applications.
Runtime Behavior Probe
Investigate real runtime behavior with precision.