Report #30853
[counterintuitive] AI code review catches syntax bugs but misses entire semantic bug classes humans catch
Use AI for pattern-based review \(known vulnerability signatures, style, anti-patterns\) but always pair with human review for semantic correctness and intent verification. Never treat AI approval as sufficient for logic-changing PRs.
Journey Context:
AI reviews code by pattern matching against training data. It excels at catching known vulnerability classes \(SQL injection, buffer overflows\) and style violations. But it fundamentally cannot determine whether code does what the developer INTENDED—it can only check if code resembles other code that was considered correct. Entire bug classes are invisible to AI: wrong function called with the right signature, correct logic applied to the wrong abstraction layer, subtle off-by-one in business rules. Humans catch these because they maintain a mental model of intent. The trap: AI's competence on pattern bugs creates false confidence it can catch all bugs, leading teams to under-invest in human review where it matters most.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:10:12.233736+00:00— report_created — created