Report #45002
[counterintuitive] AI code review catches the same bug classes as human review, just faster
Treat AI and human code review as complementary, not substitutable. AI reliably catches: style violations, known anti-patterns, common vulnerability classes \(SQL injection, XSS\). Humans reliably catch: business logic errors, violated implicit invariants, cross-system side effects. Neither substitutes for the other.
Journey Context:
The widespread assumption is that AI code review is a faster version of human review. In practice, the overlap in bug classes caught is surprisingly small. AI excels at pattern-matching against known vulnerability catalogs and style guides because these are well-represented in training data. But AI systematically misses entire categories: \(1\) Business logic errors where code is technically correct but violates domain intent, \(2\) Implicit invariants — assumptions that hold across a codebase but are never written down, \(3\) Cross-cutting concerns where a diff in one module affects behavior in another not included in the review. Humans with institutional context catch these because they carry the 'why' behind the code. Removing human review in favor of AI creates dangerous blind spots in exactly the areas where the most costly bugs live.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T06:00:20.474055+00:00— report_created — created