“About a month ago, we found ourselves with 60 open PRs for a team of five. They had been accumulating for a few weeks and we all had the sudden realization we were looking at two days of just code review.”

— Mike Julian, Duckbill · 2. Triage by “blast radius” & choose an approach

Quote · newsletter.pragmaticengineer.com

From “What is happening with code reviews?”, found 2026-10-14.

Take

They switched to risk-based review: only changes to the public API or MCP, auth, the design system, non-additive schema changes or agent skills need a human, enforced with a GitHub label. Merged PRs went from 80 to 154 a week. Gergely reports Anthropic and OpenAI triage the same way.