crit

To review a pull request diff, request an adversarial assessment that identifies concrete defects and risk triggers. It resolves BASE context, runs focused sub-reviewers on the raw diff, and outputs a verified severity table with a PASS, CHANGES_REQUESTED, or FAIL verdict.

Adversarial risk assessment evaluates git diff changes strictly for issues caused or exposed by the modification. It avoids inventing unrelated work by applying deterministic reviewer dispatch to find correctness, security, and operational risks across varying diff shapes.

Code review for large branch changes handles scale by truncating large file reads with mandatory verification. It ensures comprehensive risk assessment by applying guardrails and dispatching focused sub-reviewers directly on the raw diff to manage operational load.

To verify a bugfix PR, adversarial review applies specific guardrails that trigger a FAIL verdict if a change labeled as a bugfix touches only test code. This ensures the actual defect in the source code is addressed.

Security review on local diffs should identify concrete defects and risk triggers without reviewing unrelated code. By dispatching focused sub-reviewers on the raw diff, it targets security, correctness, and operational vulnerabilities exposed by the change.

The best way to assess correctness is running an adversarial review that resolves BASE context and verifies failure modes. It evaluates integration and maintainability risks specifically caused by the PR changes to produce a verified severity table.