Debug systematically
AI-agent skills for software engineering — works with Claude Code, Codex, Cursor
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.
2 things to look at
- 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.3 KB, 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.