Debug systematically
Find and fix a bug by root cause, not by guessing. Use when given a bug report, stack trace, or failing behavior. Follows reproduce → isolate → root-cause → fix → verify → add a regression test.From its SKILL.md
npx -y skills add vaibhavsaxena022/skills --skill debug-systematicallyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 196 tokens by cl100k_base, as published. Nobody here has run it
Debug Systematically
Fix the cause, not the symptom.
Steps
- Reproduce — get a reliable, minimal repro. If you can't reproduce it, gather more information first.
- Isolate — narrow the failing path (bisect, logs, breakpoints). One hypothesis at a time.
- Root-cause — confirm why it fails, not just where. State the actual cause.
- Fix — the smallest change that addresses the cause; no unrelated edits.
- Verify — the repro now passes and nothing else broke.
- Regression test — add a test that fails without the fix and passes with it.
Rules
- Don't patch symptoms or add defensive code that hides the cause.
- Change one thing at a time; confirm each hypothesis before moving on.
- If the root cause is a design flaw, say so — don't paper over it.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.