debugging-wizard
/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, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.
- Author
- Jeffallan ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 6
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 5
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
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, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.
Original author description
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, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.
How it works
- Core Workflow
- Reference Guide
- Constraints
- Common Debugging Commands
- Output Templates
SKILL.md preview
--- name: debugging-wizard description: 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, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis. license: MIT metadata: author: https://github.com/Jeffallan company: https://synergetic.solutions version: "1.1.0" domain: quality triggers: debug, error, bug, exception, traceback, stack trace, troubleshoot, not working, crash, fix issue role: specialist scope: analysis output-format: analysis related-skills: test-master, fullstack-guardian, monitoring-expert --- # 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)** ```bash 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)** ```bash 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)** ```bash 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)** ```bash dlv debug ./cmd/server # build & attach # (dlv) break main.go:55 # (dlv) continue # (dlv) print myVar ``` ## 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 Maintained by [@jeffallan](https://github.com/jeffallan), Principal Consultant at [Synergetic Solutions](https://synergetic.solutions) [Documentation](https://jeffallan.github.io/claude-skills/skills/quality/debugging-wizard/)
Files in this package (6)
- SKILL.md 4 KB
- references/common-patterns.md 3 KB
- references/debugging-tools.md 3 KB
- references/quick-fixes.md 3 KB
- references/strategies.md 3 KB
- references/systematic-debugging.md 13 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Jeffallan/claude-skills | 100 | MIT |
| nasac0x/code-orchestrator | 100 | MIT |
Database snapshot: 13.11.2026 · package version c1782d5e3555 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100debug
Comprehensive debugging methodology for finding and fixing bugs (formerly debugging). This skill should be used when debugging code, investigating errors, troubleshooting issues, performing root cause analysis, or responding to incidents. Covers systematic reproduction,… - 95debug-phase
Systematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation. Use when debugging errors, investigating failures, analyzing stack traces, fixing bugs, or documenting errors in error-log.md. (project) - 100root-cause-analysis
Performs systematic root cause analysis to identify the true source of bugs, errors, and unexpected behavior through structured investigation phases — not just treating symptoms. Use when a user reports a bug, crash, error, or broken behavior and needs to debug, troubleshoot, or… - 100debugger
Use this agent when you need to diagnose and fix bugs, identify root causes of failures, or analyze error logs and stack traces to resolve issues. - 100debug
Debug errors, bugs, and unexpected behavior systematically in Home Assistant integration. Use when investigating errors, analyzing stack traces, fixing bugs, or troubleshooting unexpected behavior. - 100debugging
Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.