debugging
A four-phase debugging methodology to move from root cause investigation to verified fixes.
Install
mkdir -p .claude/skills/debugging && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2082" && unzip -o skill.zip -d .claude/skills/debugging && rm skill.zipInstalls to .claude/skills/debugging
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Systematic debugging frameworks for finding and fixing bugs - includes root cause analysis, defense-in-depth validation, and verification protocolsKey capabilities
- →Investigate root causes before implementing fixes
- →Analyze patterns in recurring bugs
- →Test hypotheses about bug origins
- →Trace bugs backward through the call stack to find the original trigger
- →Validate data at multiple layers to prevent bugs
- →Verify fixes with fresh evidence before claiming completion
How it works
The skill provides sub-skills for systematic debugging, root cause tracing, defense-in-depth validation, and verification before completion. It emphasizes investigation before fixing and validation of solutions.
Inputs & outputs
When to use debugging
- →Trace bug triggers back through the call stack
- →Perform root cause analysis on production issues
- →Verify bug fixes before deployment
- →Identify patterns in failing test suites
About this skill
Debugging Skills
A collection of systematic debugging methodologies that ensure thorough investigation before attempting fixes.
Available Sub-Skills
Systematic Debugging
Location: systematic-debugging/SKILL.md
Four-phase debugging framework: Root Cause Investigation → Pattern Analysis → Hypothesis Testing → Implementation. The iron law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
Root Cause Tracing
Location: root-cause-tracing/SKILL.md
Trace bugs backward through the call stack to find the original trigger. Don't fix symptoms - find where invalid data originated and fix at the source.
Defense-in-Depth Validation
Location: defense-in-depth/SKILL.md
Validate at every layer data passes through to make bugs structurally impossible. Four layers: Entry Point → Business Logic → Environment Guards → Debug Instrumentation.
Verification Before Completion
Location: verification-before-completion/SKILL.md
Run verification commands and confirm output before claiming success. The iron law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
When to Use
- Bug in production → Start with systematic-debugging
- Error deep in stack trace → Use root-cause-tracing
- Fixing a bug → Apply defense-in-depth after finding root cause
- About to claim "done" → Use verification-before-completion
Quick Dispatch
| Symptom | Sub-Skill |
|---|---|
| Test failure, unexpected behavior | systematic-debugging |
| Error appears in wrong location | root-cause-tracing |
| Same bug keeps recurring | defense-in-depth |
| Need to confirm fix works | verification-before-completion |
Core Philosophy
"Systematic debugging is FASTER than guess-and-check thrashing."
From real debugging sessions:
- Systematic approach: 15-30 minutes to fix
- Random fixes approach: 2-3 hours of thrashing
- First-time fix rate: 95% vs 40%
How it compares
This skill enforces a structured, multi-phase debugging framework with verification protocols, contrasting with ad-hoc or guess-and-check debugging methods.
Compared to similar skills
debugging side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| debugging (this skill) | 4 | 7mo | No flags | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| chrome-devtools | 41 | 7mo | Review | Intermediate |
| bats | 9 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mrgoonie
View all by mrgoonie →You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
bats
OleksandrKucherenko
Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.
browser-daemon
noiv
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.
performance-profiling
davila7
Performance profiling principles. Measurement, analysis, and optimization techniques.
obsidian-local-dev-loop
jeremylongshore
Configure Obsidian plugin development with hot-reload and fast iteration. Use when setting up development workflow, configuring test vaults, or establishing a rapid development cycle. Trigger with phrases like "obsidian dev loop", "obsidian hot reload", "obsidian development workflow", "develop obsidian plugin".