How (not) to use AI for pull requests and code reviews

This article argues that the developer creating a pull request remains responsible for understanding its changes, impact and risks, and for testing and verification, regardless of how coding agents were used. It suggests using agents to catch bugs before opening a PR, reserving human review for decisions that matter, and having PR descriptions state in a sentence what changed and why and what feedback is requested. Tools and agents can flag risky changes such as public API modifications so humans can focus on the interesting parts.