meow:review

To automate code review against a plan, you need a multi-pass workflow that validates branch diffs, enforces architectural and security checks, and surfaces adversarial findings to determine ship readiness.

Adversarial code review uses cross-model prompts to critique branch diffs, actively uncovering edge cases, potential failures, and audit-readiness issues that standard validation might miss before merging.

You can identify drift between a branch diff and a requested plan by applying a two-pass review workflow that validates planned requirements and surfaces missing implementations before shipping.

Yes, you can enforce security, architecture, and design checks combined with test-coverage evaluation during code review to mitigate risk and ensure the branch is ready for ship.

The best way to surface actionable fixes is through a Fix-First process that identifies drift and issues during multi-pass review, persisting engineering results to gate ship commands and maintain traceability.

You should use a multi-pass code review workflow when you need to validate branch diffs against requested plans, enforce architectural checks, and perform adversarial critique prior to shipping.