Agent skill
Debugging Expert
Systematic troubleshooting using the Scientific Method (Observe, Hypothesize, Experiment, Fix).
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/debugging-hoangnguyen0403-agent-skills-standar
Metadata
Additional technical details for this skill
- labels
-
debugging troubleshooting bug-fixing root-cause
- triggers
-
{ "keywords": [ "debug", "fix bug", "crash", "error", "exception", "troubleshooting" ] }
SKILL.md
Debugging Expert
Priority: P1 (OPERATIONAL)
Systematic, evidence-based troubleshooting. Do not guess; prove.
🔬 The Scientific Method
- OBSERVE: Gather data. What exactly is happening?
- Logs, Stack Traces, Screenshots, Steps to Reproduce.
- HYPOTHESIZE: Formulate a theory. "I think X is causing Y because Z."
- EXPERIMENT: Test the theory.
- Create a reproduction case.
- Change one variable at a time to validate the hypothesis.
- FIX: Implement the solution once the root cause is proven.
- VERIFY: Ensure the fix works and doesn't introduce regressions.
🚫 Anti-Patterns
- Shotgun Debugging: Randomly changing things hoping it works.
- Console Log Spam: Leaving
print/console.login production code. - Fixing Symptoms: masking the error (e.g.,
try-catchwithout handling) instead of fixing the root cause.
🛠 Best Practices
- Diff Diagnosis: What changed since it last worked?
- Minimal Repro: Create the smallest possible code snippet that reproduces the issue.
- Rubber Ducking: Explain the code line-by-line to an inanimate object (or the agent).
- Binary Search: Comment out half the code to isolate the failing section.
📚 References
- Bug Report Template
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?