independent-review-gatelisted

## The rule Your own review and a green test suite are not enough. You're invested in the approach, so you read past your own mistakes, and the tests only cover what you already thought to check. Before calling complex work done, have someone or something with no stake review the whole change. A fresh set of eyes catches the defect that's obvious in hindsight and invisible to you. This is the non-optional version of superpowers' requesting-code-review: the review is not a step to skip when the suite is green, because the green suite is exactly what can't be trusted alone — and the fix you make after the review gets re-reviewed too. ## Fires when Finishing a feature or a spec. Before merging. Before claiming "done" on anything non-trivial, or anything that ships to other people. ## How to apply Hand the full diff to an independent reviewer with explicit angles to check: correctness, edge cases, the branches no test touches, backward compatibility. Fix the blockers and cover each one with a test. Then re-review the fix itself — a second pass catches the inverted-fix mistake faster than a new test would. The green suite is not the gate. The independent verdict is. ## Worked example Your change to a payment client passes all 200 tests and your own read-through. A reviewer with fresh eyes notices that one branch — the error path no test covers — has an inverted condition: it retries on success and gives up on failure. The suite was green because it only ran the happy pa