omk-code-review

To run an adversarial code review, provide the proposed pull request diff to assess correctness, security, type safety, data consistency, and error handling before merge. The review produces a verdict with prioritized blocking and non-blocking issues, test gaps, and suggested fixes.

Adversarial diff analysis evaluates a proposed code change as if it is going directly into production. It enforces a review focused on preventing incorrect, insecure, or regression-prone merges by flagging critical correctness and security issues.

Identify blocking issues and security vulnerabilities by analyzing the code diff for type-safety, data-consistency, and error-handling problems. The review output highlights these critical flaws that must be fixed before a production merge.

Yes, you can check for missing test coverage and regression risks. The review identifies performance regressions, unnecessary scope creep, and test gaps within the diff, providing suggested fixes to ensure maintainability.

Yes, the code review process works without external dependencies. It directly analyzes the proposed code changes to produce a clear list of reviewed files, a merge verdict, and prioritized issues based solely on the provided diff.

The best way to prevent insecure or risky code is to enforce a production-merge review on every diff. This approach catches bugs, security issues, and regressions by requiring a thorough assessment of correctness and maintainability before merging.