The version that boosted improvement for me: make the reviewer a different model than the one that wrote the code, and prompt it to be adversarial: refute rather than green light. A launch-blocker fix that compiled and passed every test still had 3 real bugs - the adversarial cross-vendor pass was the only thing that caught them. Same-model self-review mostly rubber-stamps. That being said, I usually run same-vendor in parallel though, just for instant consensus on the major issues, but I direct fixes based on the adversarial model. The "survive an attack" part is key.