bug-diagnosis
Installation
SKILL.md
Bug Diagnosis
A disciplined loop for bugs that survived the first obvious fix. The order is fixed: build a signal that says "bug present / bug absent" in seconds, write down competing explanations with predictions that could prove them wrong, test the cheapest likely one, narrow the search space by halving, and lock the cause in with a regression test that was seen failing. Most wasted debugging time comes from skipping the first step and reading code to build a theory with nothing to check it against.
When to use this skill
- A bug resisted a first fix — the patch went in and the symptom came back, or moved
- The failure is intermittent — passes locally, fails in CI one run in five
- A regression appeared between two releases and nobody knows which change caused it
- The symptom is far from the cause — wrong totals, corrupted records, a hang with no error
- A performance regression needs a measured cause rather than a guess
- Logs or traces need sharing with a teammate, vendor or assistant and may contain credentials