In 2024 I wrote about fixing code review after it became our team's bottleneck. Everything in that post assumed a person had written the code. Most of my code is now written by an agent, and those PRs can wait a week for review.
This post goes back through my old review hierarchy and asks who checks each layer now. It also covers what I check instead, and where that approach breaks.
On a long-running headless multisite project, our code review process slowly spiralled out of control, with 100+ open PRs, slow turnarounds, constant context-switching, and frustrated engineers. We fixed it by reframing how we think about reviews, creating a clear hierarchy, and making readability the foundation. This is the story of how we made code reviews calmer, faster, and far more...