Debugging
Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/debugging
🧠The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.
npx -y skills add ComeOnOliver/skillshub --skill debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Systematic troubleshooting using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.
SKILL.md
1.6 KB, 322 tokens by cl100k_base, as published. Nobody here has run it
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.