A coding agent finishes a feature, opens a merge request and starts the next task. The engineers who need to understand the first change are still reviewing yesterday's work.

Faster generation can produce bigger merge requests, more merge requests, or both. If meaningful review cannot keep pace, the delivery queue grows even while the coding work appears to accelerate.

My approach would combine stronger automated checks, approval rules that match the consequences of a change, and AI assistance for reviewers. Gradual release then limits initial exposure and gives the team a chance to detect problems before expanding it. Each part addresses a different constraint.

Smaller merge requests solve part of the problem

Thirty small-to-medium merge requests are not necessarily easier to review than ten large ones. That comparison depends on what the changes do, how they interact and how much context each reviewer must reconstruct.

Small, coherent changes still help.…