JoelBonito/systematic-debugging
.agents/skills/systematic-debugging/SKILL.md
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add JoelBonito/gestion-chs systematic-debuggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 4:45 PM21.0s1 file scanned
SKILL.md
- name:
- systematic-debugging
- description:
- 4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
- allowed-tools:
- Read, Glob, Grep
Systematic Debugging
Source: obra/superpowers
Overview
This skill provides a structured approach to debugging that prevents random guessing and ensures problems are properly understood before solving.
4-Phase Debugging Process
Phase 1: Reproduce
Before fixing, reliably reproduce the issue.
## Reproduction Steps
1. [Exact step to reproduce]
2. [Next step]
3. [Expected vs actual result]
## Reproduction Rate
- [ ] Always (100%)
- [ ] Often (50-90%)
- [ ] Sometimes (10-50%)
- [ ] Rare (<10%)
Phase 2: Isolate
Narrow down the source.
## Isolation Questions
- When did this start happening?
- What changed recently?
- Does it happen in all environments?
- Can we reproduce with minimal code?
- What's the smallest change that triggers it?
Phase 3: Understand
Find the root cause, not just symptoms.
## Root Cause Analysis
### The 5 Whys
1. Why: [First observation]
2. Why: [Deeper reason]
3. Why: [Still deeper]
4. Why: [Getting closer]
5. Why: [Root cause]
Phase 4: Fix & Verify
Fix and verify it's truly fixed.
## Fix Verification
- [ ] Bug no longer reproduces
- [ ] Related functionality still works
- [ ] No new issues introduced
- [ ] Test added to prevent regression
Debugging Checklist
## Before Starting
- [ ] Can reproduce consistently
- [ ] Have minimal reproduction case
- [ ] Understand expected behavior
## During Investigation
- [ ] Check recent changes (git log)
- [ ] Check logs for errors
- [ ] Add logging if needed
- [ ] Use debugger/breakpoints
## After Fix
- [ ] Root cause documented
- [ ] Fix verified
- [ ] Regression test added
- [ ] Similar code checked
Common Debugging Commands
# Recent changes
git log --oneline -20
git diff HEAD~5
# Search for pattern
grep -r "errorPattern" --include="*.ts"
# Check logs
pm2 logs app-name --err --lines 100
Anti-Patterns
❌ Random changes - "Maybe if I change this..." ❌ Ignoring evidence - "That can't be the cause" ❌ Assuming - "It must be X" without proof ❌ Not reproducing first - Fixing blindly ❌ Stopping at symptoms - Not finding root cause
Related Skills
JoelBonito/n8n-orchestration
tools
VerifiedTrustedCommunity
n8n workflow automation principles, patterns, and validation. Expression syntax, node configuration, MCP tools usage, code node patterns.
SKILL.mdUpdated Apr 16, 2026
JoelBonito/squads/.templates/specialist/skills/example
testing
VerifiedTrustedCommunity
# Example Skill > Template skill for specialist squads. Replace with your domain-specific knowledge. ## Overview This skill provides domain-specific knowledge and patterns for the squad. ## When to Use - When the squad needs domain expertise - When applying domain-specific patterns - When reviewing domain-related outputs ## Key Principles 1. **Principle 1:** Description of the first principle 2. **Principle 2:** Description of the second principle 3. **Principle 3:** Description of the th
SKILL.mdUpdated Apr 16, 2026
JoelBonito/webapp-testing
development
VerifiedTrustedCommunity
Web application testing principles. E2E, Playwright, deep audit strategies.
SKILL.mdUpdated Apr 16, 2026
JoelBonito/web-design-guidelines
development
VerifiedTrustedCommunity
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
SKILL.mdUpdated Apr 16, 2026