ck:code-review

To run an adversarial code review on a pull request, provide the PR number to trigger a three-stage pipeline: spec compliance, code quality review, and a red-team stage that actively tries to break the changes to expose security vulnerabilities and failure modes.

A red-team code review exposes critical security vulnerabilities, false assumptions, race conditions, resource exhaustion, and other failure modes that typical style or checklist reviews miss, preventing risky merges and regressions.

Yes, you can review staged or unstaged pending diffs by using the --pending input mode, applying the full adversarial review pipeline to identify security vulnerabilities and failure modes in your local changes before they are committed.

You can scan an entire codebase for security flaws by triggering a full codebase scan, which performs an engineer-led audit using the adversarial review pipeline to detect vulnerabilities, false assumptions, and resource exhaustion across the project.

Structured code review findings include severity, category, file:line locations, attack descriptions, impact assessments, and remediation guidance, providing actionable and verifiable evidence for identified security vulnerabilities and failure modes.

Yes, adversarial code review works with specific commit hashes by resolving the review target from the hash and applying the three-stage pipeline to expose security vulnerabilities, race conditions, and false assumptions introduced in that commit.