Code review with AI

In the last lesson we learned to write a PR description that summarizes several commits. Now, once the PR is open and CI has run, comes the step that's easiest to skip: reading the diff itself, exactly as you'd read a human developer's PR. Green CI means the code didn't break an existing test — it d

Checking a diff an agent wrote is like inspecting a package delivered to your door before you sign for it — it's not enough that the box is sealed and looks fine from outside, you need to open it and confirm what's inside is really what you ordered, not something extra.

PR diff: The full view of every added and removed line in a PR, in unified diff format; this is what you read line by line to check whether a change does exactly what was asked.
request changes: A review verdict that blocks the merge until the author fixes specific points; different from a free-text comment — it actually prevents merging until the point is addressed.
green CI (and what it doesn't mean): Confirmation the code passed lint, type-checking, and existing tests; it does not confirm the diff is scoped to what the ticket asked, and doesn't check boundary values no test covers.
unrelated change bundled in a diff: An edit that appears in the same PR but isn't related to the requested fix; even if it slips through CI quietly, it should be pulled out or reviewed separately.