ck:code-review

Run an adversarial security review on a pull request diff by targeting the specific PR to execute a three-stage pipeline enforcing spec compliance, code quality, and red-team failure mode analysis.

The best way to verify spec compliance before merging is using an evidence-first code review process that gates code quality and adversarial security stages, preventing completion until verification evidence is provided.

Yes, you can scan your whole codebase for security flaws by running full-repo audits with optional parallel multi-reviewer coverage to manage larger scopes and uncover hidden false assumptions.

Yes, the code review process works with pending local changes by resolving input-mode targeting to review exact local diffs, keeping scope accurate and preventing guesswork before commit.

Adversarial red-teaming prevents superficial code reviews by applying an always-on security stage with scope gating to attack vulnerabilities and failure modes, eliminating risky guesswork through evidence-based detection.

Use parallel multi-reviewer coverage for commit diffs when managing larger scopes during full-codebase audits, ensuring comprehensive adversarial analysis without generating trivial noise from scope gating.