Stats
Actions
Tags
Provides systematic debugging methodology for thorough root cause analysis with evidence-based investigation. Use this skill when investigating code, analyzing bugs, tracing errors, or understanding unexpected behavior.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-guidelines-debugging:debugging-processThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Real-Time Reporting**: Share findings immediately with `file:line` references. Report "Checking [X] at [location]" → "Found [Y], suggests [Z]"
file:line references. Report "Checking [X] at [location]" → "Found [Y], suggests [Z]"1. "Investigating [X] by checking [Y]"
2. "Found [this] at [location:line]. Suggests [interpretation]"
3. "Based on this, checking [next location]"
4. Root cause identified → Apply fix
DO: Use file:line references, share evidence progressively, trace to origin, explain causal chain
DON'T: Rush to fix, hide investigation process, fix symptoms not causes
Problem: App crashes on submit
Why? → Exception in validation
Why? → Receives null value
Why? → Form data not initialized
Why? → Component mounts before API response
Why? → Race condition
→ Fix: Correct initialization order
npx claudepluginhub kokuyouwind/claude-plugins --plugin dev-guidelines-debuggingEnforces systematic root cause investigation for bugs, test failures, and unexpected behavior through four phases: investigation, pattern analysis, hypothesis testing, and implementation.
Enforces systematic root cause analysis before fixes for bugs, test failures, unexpected behavior, performance issues, and build failures.
Guides systematic root-cause debugging for bugs, test failures, unexpected behavior, performance issues, and build failures via reproduction, evidence gathering, and data flow tracing before fixes.