code-auditor-gate

Adversarial code review identifies security and quality risks in code changes, ranking findings by severity and proposing concrete fixes. It validates correctness, memory safety, portability, and architecture invariants across changed files to ensure robust output.

To enforce a mandatory security checklist during code review, apply predefined security checks to changed files. This produces severity-ranked findings with concrete mitigations and concludes with an explicit gate status and residual risks.

A severity-fixed gate status in code review is an explicit decision point indicating whether changed files pass security and quality checks. It includes residual risks, providing a clear go or no-go signal based on ranked findings.

Yes, you can review architecture invariants and memory safety in changed files. The review process validates correctness, memory safety, portability, and maintainability, focusing on predefined security checks to identify potential risks.

Code review works with architecture docs and changed files by reading both during the analysis. It validates architecture invariants and applies predefined security checks to produce severity-ranked findings with concrete fixes.