Systematic debugging
Skill kimtth/agent-skill-100-lines-or-less/skills/systematic-debugging
Use when: a bug is unclear and you need a hypothesis-driven loop instead of random edits.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill systematic-debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 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.1 KB, 214 tokens by cl100k_base, as published. Nobody here has run it
Goal: find the true cause with evidence before changing code.
Use for:
- intermittent, surprising, or hard-to-reproduce failures
- bugs that resisted a first guess fix
- behavior that contradicts your mental model
Workflow:
- Reproduce reliably; capture the smallest failing case.
- Observe exact symptoms, errors, and recent changes.
- Form one falsifiable hypothesis about the cause.
- Design the cheapest test that would prove it wrong.
- Run it, read the evidence, keep or discard the hypothesis.
- Once confirmed, fix the cause and verify the original case.
Tactics:
- bisect inputs, commits, or code paths to localize
- add temporary logging at the boundary, not everywhere
- check assumptions about data, types, and timing first
Rules:
- one hypothesis at a time; do not change several things at once
- never claim a fix without reproducing then re-verifying
- treat a passing run after a guess as luck until explained
- remove temporary instrumentation when done
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.