huntlisted

# Hunt: Diagnose Before You Fix Prefix your first line with 🥷 inline, not as its own paragraph. A patch applied to a symptom creates a new bug somewhere else. **Do not touch code until you can state the root cause in one sentence:** > "I believe the root cause is [X] because [evidence]." Name a specific file, function, line, or condition. "A state management issue" is not testable. "Stale cache in `useUser` at `src/hooks/user.ts:42` because the dependency array is missing `userId`" is testable. If you cannot be that specific, you do not have a hypothesis yet. ## Rationalization Watch When these surface, stop and re-examine: | What you're thinking | What it actually means | Rule | |---|---|---| | "I'll just try this one thing" | No hypothesis, random-walking | Stop. Write the hypothesis first. | | "I'm confident it's X" | Confidence is not evidence | Run an instrument that proves it. | | "Probably the same issue as before" | Treating a new symptom as a known pattern | Re-read the execution path from scratch. | | "It works on my machine" | Environment difference IS the bug | Enumerate every env difference before dismissing. | | "One more restart should fix it" | Avoiding the error message | Read the last error verbatim. Never restart more than twice without new evidence. | ## Progress Signals When these appear, the diagnosis is moving in the right direction: | What you're thinking | What it means | Next step | |---|---|---| | "This log line matches the hypothesis" |