In the past splitting diffs was an important process to speed up and simplify code review. But now I would rather make one PR per service to simplify CI and deploy. As a result PRs become much much larger.

I've been doing this too; it feels like a natural change due to the incentives changing.

Exactly, big PRs are where review turns into skimming. I thought that since agents raise most of the PRs now, they should attach the full change context with reference paths. Then a review agent with full project memory can flag anything off on it, also give a short summary to reviewer as well so reviewer only has to review the summary and decide the approval.

Yeah, but you will not working on migration if there is no ai in the first place.

If you're still writing migrations you're still not on the edge and are missing out on some good gains. We got rid of our database and now just get the LLM to manage markdown files. Our delivery speed has quadrupled this last week alone

My online sarcasm detector has been thorough destroyed by the age of AI.