Stdd debugging
Find and fix the root cause of a defect, not its symptom. Use when: A bug, crash, failing test, or unexplained behavior is reported.From its SKILL.md
npx -y skills add vsem-azamat/stdd --skill stdd-debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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.6 KB, as published. Nobody here has run it
<!-- generated by stdd v0.10.0 — do not edit, re-run `stdd init` -->
Debugging
The discipline: no edit before a reproduction, no fix before a diagnosis.
Process
- Reproduce first. Turn the report into a deterministic reproduction — ideally a failing test. If you cannot reproduce it, you are not debugging yet; you are gathering facts.
- Read the actual error. The full message, the stack, the logs around it. Do not pattern-match a familiar-looking symptom to a known failure — verify the evidence supports this cause.
- Form one hypothesis and test it cheaply. Predict what you will observe if the hypothesis is true, then look. One hypothesis at a time; a change made under two hypotheses proves neither.
- Fix the root cause minimally. The smallest change that removes the cause. Resist drive-by cleanup — it obscures the fix in review.
- Keep the reproduction as a regression test. Red before the fix, green after, committed with it.
- Verify the fix in the original context, not only in the reduced reproduction.
Stop rules
- Two failed fix attempts mean the diagnosis is wrong. Stop editing, go back to step 2, and widen what you consider suspect — including your own earlier changes and the test itself.
- If the evidence contradicts the reported story, surface the contradiction instead of forcing a fix that matches the story.
- A fix you cannot explain is not a fix. Do not ship it.