Bug autopsy
Claude Code skills for non-technical founders, solopreneurs & one-person companies running an AI engineering team — no coding experience required. Six battle-tested skills + a real token-burn postmortem.
npx -y skills add lightarktech/founder-coding-skills --skill bug-autopsyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 15 days oldThe repository was created 15 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
Structured diagnosis for bugs — no guess-and-patch. Use when something is broken, throwing, failing, or slow and the cause isn't already proven.
SKILL.md
1.9 KB, 407 tokens by cl100k_base, as published. Nobody here has run it
The expensive failure mode isn't the bug — it's an AI guessing at the cause and "fixing" code it never proved guilty. Guess-patches breed regressions, and three guess-patches deep, nobody knows what the system even does anymore.
For the full catalog of ways to build and tighten a repro loop, see building-repro-loops.md.
The discipline
- Build a red light first. Before any theory, construct one command that reliably shows the bug — a failing test, a script, a curl. If you can't trigger it on demand, you don't understand it yet; keep working on the trigger, not the theory. For flaky bugs, raise the reproduction rate until it's debuggable — loop it 100×, pin the randomness, narrow the timing.
- Shrink it. Cut inputs and steps one at a time until everything that remains is load-bearing. A minimal repro shrinks the suspect list for free.
- List 3 candidate causes before testing any. One-hypothesis debugging anchors on the first plausible story. Each candidate must make a testable prediction: "if X is the cause, changing Y makes it disappear."
- Test one variable at a time. A probe that changes two things proves nothing.
- Fix the proven cause only. No drive-by cleanups in the same change.
- Re-run the red light — now green — plus the full test suite. Turn the repro into a permanent regression test.
Hard rules
- No repro, no patch. "It's probably X" is not a diagnosis.
- Production systems get read-only inspection; every change goes through the normal review path.
- Close with a report: root cause, lines changed, proof of the fix.
Success criteria
The commit message names the proven cause. The repro is now a regression test. Nothing unrelated changed.
What ships with it: 1 file
2.5 KB alongside SKILL.md
- building-repro-loops.md2.5 KB