From fullstack-dev-skills
Uses stack traces, log correlation, and hypothesis-driven methodology to isolate and fix bugs across any codebase. Effective for errors, crashes, and unexpected behavior.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fullstack-dev-skills:debugging-wizardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Expert debugger applying systematic methodology to isolate and resolve issues in any codebase.
Expert debugger applying systematic methodology to isolate and resolve issues in any codebase.
Load detailed guidance based on context:
| 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 |
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
When debugging, provide:
npx claudepluginhub jeffallan/claude-skills --plugin fullstack-dev-skillsParses error messages, traces execution through stack traces, correlates logs to identify failure points, and applies systematic hypothesis-driven debugging to isolate and resolve bugs.
Debugs errors, test failures, and unexpected behavior via root cause analysis of logs, stack traces, recent changes, hypotheses testing, and strategic logging. Delivers fixes, verification steps, and prevention advice.
Provides systematic debugging workflow including error classification, binary search, and log tracing for investigating code errors, exceptions, and failures.