Measure

Merge rate

You might say: merge share, accepted PR rate

The share of agent-assisted pull requests that merge during a stated period. Keep the denominator and time window fixed when comparing task types or throttles.

What it does
Shows how much generated work survives checks and review to become repository history.
Ask
Of the agent pull requests opened in this window, how many merged, closed, or remain open?
Typical
83.8% accepted and merged in a 567-PR Claude Code sample; 54.9% merged without further modification.
Trouble
A high percentage hides many abandoned PRs, or merges rise while change failures and review wait rise too.

What to look for

  1. A dashboard percentage labelled merged over opened agent PRs
  2. Counts for merged, closed, and open pull requests
  3. A trend split by task type or model

Sources

  1. Miku Watanabe, On the Use of Agentic Coding: An Empirical Study of Pull Requests on GitHub, AbstractThe results indicate that 83.8% of these agent-assisted PRs are eventually accepted and merged by project maintainers, with 54.9% of the merged PRs are integrated without further modification.

Use it on your project

teardown-apply: hold "Merge rate" (merge-rate) from the teardown at https://teardownatlas.com/software-factory/ against my project

Paste it into a coding agent that has the teardown skills.

An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal