# Scaling Engineering Velocity with Automated Small-Change Reviews Imprint optimizes pull request workflows by automating approvals for low-risk, high-confidence code changes. - **Source:** [Irrational Exuberance](https://lethain.com) - **Published:** 2026-10-17 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/465b63cf-649a-4794-9ac0-4757960858c9 ## Engineering Velocity and Quality Imprint engineers are merging four times more pull requests than two years ago, with some teams achieving a ten-fold increase. Despite this surge in velocity, incident rates dropped significantly, with critical incidents falling 78% half-over-half. This data challenges the traditional belief that increasing shipping speed inherently compromises software quality and system stability. ## The Review Bottleneck Challenge As merge volume increased, the p50 pull request review time climbed from 33 minutes to 77 minutes. This rising latency correlates directly with the higher volume of code changes. Recognizing this as a primary bottleneck, the team sought to evolve their review process rather than simply adding more human reviewers to the queue. ## Defining Small-Change Criteria A pull request qualifies as a small-change if it contains under 1,000 lines, has no p1 or p2 AI-bot findings, and involves an author with ten-plus prior merges in that service. Changes must impact fewer than three backend services or one frontend service, while shared libraries and sensitive financial paths remain strictly excluded. ## Automated Approval Mechanisms The system uses a non-human-modifiable GitHub check to verify eligibility. Once validated, an internal skill named review-small-change automatically approves the pull request. This tool is binary, offering only approve or ignore options, which prevents the proliferation of meat proxy reviews that often stall development cycles by adding unnecessary, low-value human commentary. ## Systemic Error Responsibility Imprint established a social expectation that any errors originating from a small-change are systemic failures. Rather than blaming individuals, the team focuses on improving their AI-code-review bot, CI/CD pipelines, and verification harnesses. This approach shifts the burden of quality from manual human gatekeeping to robust, automated, and continuously improving infrastructure. ## Avoiding Meat Proxy Reviews Meat proxy reviews occur when overwhelmed teams use local harnesses to generate excessive, often conflicting comments on pull requests. This creates an illusion of thoroughness while actually slowing down development. Imprint argues that teams achieve better outcomes by investing in centralized review mechanisms and automated verification loops rather than manual, performative code feedback. ## Centralized Orchestration with Fleet Beyond small-change, the team utilizes a centrally orchestrated harness called fleet to implement and verify software in controlled cloud environments. Similar to Stripe’s Minions, fleet identifies the necessary number of independent reviewers for any given change. For safe evaluations, this can reduce the requirement to a single human reviewer for efficiency. ## Strategic Future Outlook Currently, 10% of changes qualify as small-change, providing fast approvals for eligible code. Success depends on expanding this percentage by enhancing verification mechanisms for complex, low-scale domains. While the transition challenges long-held engineering dogmas, the team views this continuous reevaluation of best practices as essential for maintaining competitive development velocity. ## Sources covering this story - https://lethain.com/small-changes/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._