# 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.

- Skill: `belentani7/debugging-wizard` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add belentani7/debugging-wizard`
- Raw SKILL.md: https://api.skillmd.com/api/skills/belentani7/debugging-wizard/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: belentani7 (https://skillmd.com/u/belentani7)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/belentani7/debugging-wizard

---


# 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

## Common Debugging Commands

**Python (pdb)**
```bash
python -m pdb script.py
# b 42  — set breakpoint at line 42
# n     — step over
# s     — step into
# p var — print variable
# bt    — print full traceback
```

**JavaScript (Node.js)**
```bash
node --inspect-brk script.js
# In Chrome: open chrome://inspect
```

**Git bisect (regression hunting)**
```bash
git bisect start
git bisect bad
git bisect good v1.2.0
# Test, then: git bisect good / git bisect bad
git bisect reset
```

## Output Templates

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

## 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
- Leave console.log/debugger statements in code