Engineers have stopped reviewing PRs
7 hours ago
- Reviewing an AI coding session means evaluating the entire run, not just the diff, because key decisions happen during the session.
- Habit 1: Preserve the original brief verbatim in the pull request description, including corrections that changed scope.
- Habit 2: Keep the transcript retrievable using tools like tmux, script, or CLI exports (e.g., Claude Code's /export, Codex CLI session files).
- Habit 3: Review in five layers: brief, corrections, abandoned paths, overrides, and running behavior—each catches failures the diff hides.
- Habit 4: Make a second person the default reviewer for agent-assisted PRs to counter expectation bias.
- Session review takes 10-15 minutes and can be practiced with discipline; tools like AQ reduce friction by making the session a shared artifact.