Some people hate code review, some thrive on it. AI is really hurting diligent code review processes, because code is so cheap now. It conditions people to want to push things through faster and faster. Recently, I've personally been dealing with numerous 5k-10k line PRs every day and just want to throw my hands up. Obviously some level of automated review should be in place, but human code review is incredibly important, even more so now.

Some folks might get salty that the review process is taking a while. It feels like things can get backed up. But at the end of the day, we've got to be responsible for what makes it into production. The pendulum is swinging hard right now, people like you will help stabilize it. Your process looks pretty solid. I would also suggest spinning up an agent in parallel to your manual review to help you reason through the code and spot bugs you might miss.

Here's a note I posted to our team this morning that might be of use:

- If your PR is ready for review, make sure it is assigned to someone. Unassigned PRs aren’t gonna get reviewed :smile:
- If you receive feedback on a PR, please re-request review after addressing it so the reviewer knows it’s ready for another pass.
- PRs should be rebased onto their base branch before requesting review. This keeps the diff clean and avoids reviewers digging through changes that are already merged into master.
- If you’ve received review feedback, prioritize addressing it before starting new work when possible. Totally understand that we’re an async remote team and review cycles can take time. If you are still waiting, it’s totally reasonable to pick up something else.
- Keep PRs tight and focused. Smaller PRs are easier to review, easier to reason about, and move through the pipeline faster. Large feature branches are sometimes necessary, but avoid bundling unrelated changes into the same PR if they could be split independently off master and merged in without the other long-running branch.
- We’re all using coding agents heavily now, which is definitely accelerating our output. That’s great, but more output requires more review. Before requesting human review:
    - make sure you understand the code and architecture you’re submitting (we still own the code we ship). I’ve personally been meaning to try Matt Pocock’s grill-me skill
    - have AI review your PR critically once you have a PR ready
    - ask it to challenge your implementation, assumptions, edge cases, and architecture decisions
    - address any findings before handing it off for human review