adversarial-code-review

Use when independently reviewing working-tree changes, staged changes, commits, or pull requests before merge, especially AI-generated code, large or cross-module changes, weak or rewritten tests, requirement drift, suspicious scope, unverifiable completion claims, or security, transaction, concurrency, performance, dependency, compatibility, and operational risks.