Install
Terminal · npx$
npx skills add https://github.com/jeffallan/claude-skills --skill debugging-wizardWorks with Paperclip
How Debugging Wizard fits into a Paperclip company.
Debugging Wizard drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.
S
SaaS FactoryPaired
Pre-configured AI company — 18 agents, 18 skills, one-time purchase.
$27$59
Explore packSource file
SKILL.md105 linesExpandCollapse
---name: debugging-wizarddescription: 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: MITmetadata: author: https://github.com/Jeffallan 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 steps2. **Isolate** - Narrow down to smallest failing case3. **Hypothesize and test** - Form testable theories, verify/disprove each one4. **Fix** - Implement and verify solution5. **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)**```bashpython -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)**```bashnode --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)**```bashgit bisect startgit bisect bad # current commit is brokengit 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 commitgit bisect reset``` **Go (delve)**```bashdlv 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 issue2. **Evidence**: Stack trace, logs, or test that proves it3. **Fix**: Code change that resolves it4. **Prevention**: Test or safeguard to prevent recurrence