Agent skill
debugging-process
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/debugging-process
SKILL.md
Debugging Process
Instructions
Core Principles
- Real-Time Reporting: Share findings immediately with
file:linereferences. Report "Checking [X] at [location]" → "Found [Y], suggests [Z]" - Root Cause First: Use 5 Whys technique. Fix the source, not symptoms.
Investigation Pattern
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
Anti-Patterns
- Adding try-catch without understanding why it throws
- Null-checks everywhere instead of understanding cause
- Guessing solutions (e.g., setTimeout hoping it helps)
- Presenting only conclusions without evidence
DO / DON'T
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
Examples
5 Whys Example
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?