← ClaudeAtlas

vibe-debuglisted

Find the root cause before changing anything — for a bug, a test failure, a check that went red, or behaviour nobody can explain. Use when the cause is not yet known, when a previous fix did not hold, or when the same symptom has come back.
ZEST-im/vibe-engineering · ★ 7 · Code & Development · score 81
Install: claude install-skill ZEST-im/vibe-engineering
# Vibe Debug — Find the cause before you touch anything The failure this prevents is not "wrong fix". It is **a fix that makes the symptom go away while the cause stays**, because that one comes back later, bigger, and by then everybody believes the thing was fixed. Reach for this when the cause is not yet known. Not every edit needs it — a typo in a string is a typo in a string. But a bug you can explain in one sentence is one you already investigated, and a bug you cannot is one where guessing costs more than looking. ## The rule **No fix before the cause is named.** You can name it or you cannot. If you cannot, you are still in step 1, whatever the pressure says. Systematic is not the slow path — it is the path that does not need redoing. --- ## 1. Find where it breaks **Read the error completely.** All of it, including the parts that look like noise. Line numbers, paths, exit codes. An error message is usually the only part of the system that is telling you the truth without being asked. **Reproduce it.** Exact steps, every time. If it only sometimes happens, that *is* the finding — go collect more data rather than fixing on one sample. > **Emptying the environment is not the same as turning the feature off.** > This repo reproduced a CI failure with `env -i` and it passed, because macOS git > *guessed* the identity that CI did not have. `user.useConfigOnly` turned the guessing > off and the failure appeared. A reproduction that passes may mean the reproduction