AI-generated code deserves at least normal scrutiny because fluent syntax can hide false assumptions, invented interfaces, insecure patterns, or unintended scope.
Read the complete diff and compare its behavior with the requirement.
Verify unfamiliar APIs and dependencies against version-matched, authoritative sources.
Test boundary cases, failures, authorization, data handling, secrets, and external calls.
Review generated tests independently; they may repeat the implementation's mistake.
The submitter owns every line. Set review depth from the change's impact and reversibility, not from how quickly or confidently the code appeared.
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
