Report #52175
[counterintuitive] Human review of AI-generated code reliably catches AI errors
Implement structured review checklists targeting known AI failure modes \(implicit invariant violations, edge cases, security anti-patterns, specification gaming\) rather than relying on free-form review. Unstructured human review of AI code has alarmingly low error detection rates because AI code is optimized to look correct.
Journey Context:
The assumption is that human review is a reliable safety net for AI-generated code. Research shows this is dangerously wrong. When humans review AI-generated code, they exhibit: \(1\) Automation bias—accepting AI suggestions that look plausible without deep scrutiny, \(2\) Anchoring—being influenced by the AI's framing of the problem and solution approach, \(3\) Asymmetric fatigue—AI generates code faster than humans can review it, leading to review shortcuts. Perry et al. found that developers with AI assistants wrote more security vulnerabilities, not fewer, despite the AI's suggestions looking correct. The key insight: AI-generated code is optimized to look correct—proper formatting, conventional patterns, plausible logic—making it harder for humans to spot errors than in obviously messy human-written code. Messy code triggers reviewer vigilance; clean-looking AI code triggers reviewer trust. Structured checklists counteract this by forcing reviewers to check specific failure modes rather than relying on gut feel.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:04:14.648575+00:00— report_created — created