debugging
Find the cause before fixing. Use for a bug, failing test or unexpected behavior, before proposing a change.
SKILL.mdplugins/bud/skills/debugging/SKILL.md
GitHubDebugging
Find the cause first. A fix without one is a guess that moves the symptom.
- Reproduce it. Get the exact input, command and output. If it won't reproduce, say so and stop guessing.
- Read the evidence. The full error, the stack, the log lines around it, and
git logfor what changed lately. - Narrow it. Compare a working case with the broken one. Bisect by commit, input or code path, and change one thing at a time.
- Say the cause in one sentence and the check that shows it: "X fails because Y; Z proves it." Run the check.
- Fix that cause, with the test that would have caught it (see
bud:code-style). - Show the same reproduction passing (see
bud:verify).
If three fixes in a row haven't worked, the cause is wrong. Go back to step 2 and tell Jason what you ruled out.