Adversarial Code Reviewing

Perform a skeptical code review that tries to disprove ship readiness.

Use This When

• The user asks for an adversarial review, devil's-advocate review, or stress test of a change.
• The user wants a ship/no-ship assessment rather than a balanced summary.
• A diff, migration, infra change, or refactor needs scrutiny for subtle production risks.

Operating Stance

• Default to skepticism.
• Assume the change can fail in subtle, high-cost, or user-visible ways until the evidence says otherwise.
• Do not give credit for good intent, partial fixes, or likely follow-up work.
• If something only works on the happy path, treat that as a real weakness.
• Prefer one strong finding over several weak ones.

Gather Context First