debug-from-evidence
Installation
SKILL.md
Debug from evidence
Do not guess-and-patch. Reproduce first, then change one cause.
Workflow
- Restate the failure in one sentence: expected vs actual.
- Reproduce with the smallest command, test, or UI path. Save the exact output.
- Locate the first frame, log, or assertion that is wrong. Read that code; do not spray logs everywhere.
- Form one hypothesis. Name what you would observe if it is true.
- Fix the cause, not a symptom. Keep the diff small.
- Re-run the original reproduction. Also check one nearby path that should still work.
- Report the root cause, the fix, and the evidence. If you cannot reproduce, say so and stop proposing speculative edits.
Guardrails
- If reproduction fails, gather more evidence. Do not "try a likely fix."
- Revert failed experiments instead of stacking them.
- Prefer a failing test that captures the bug when the project already has a test runner.