Review and debug

How to review code, hunt bugs, and verify fixes without creating noise or whack-a-mole loops.

Source: gstack review/SKILL.md, investigate/SKILL.md, canary/SKILL.md, CLAUDE.md.

Investigate's Iron Law

"NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Fixing symptoms creates whack-a-mole debugging. Every fix that doesn't address root cause makes the next bug harder to find."

Four phases, in order:

1. Investigate — read the data flow before guessing
2. Analyze — what's the actual cause vs the symptom
3. Hypothesize — name the hypothesis explicitly
4. Implement — only after the first three

The 3-strike rule