Review economics
jd/tenacity
Read from the 100 most recently merged pull requests ·
Pull requests with attributed agent authorship took only 0.4× the reviews submitted of the rest.
≥37%
Attributed
a floor
42
Attributed PRs
58
Other PRs
100
Read
Attributed — the latest 5
#664 Improve inline type annotations
1 reviews · 8.7d to merge
#672 chore: let dependabot update Python dependencies
0 reviews · 2h to merge
#673 test: check decorator typing statically instead of with typeguard
0 reviews · 2h to merge
#671 chore: pin mypy to 2.3.0
0 reviews · 0h to merge
#670 chore: pin ruff to 0.16.1
0 reviews · 0h to merge
The rest — the latest 5
#682 refactor: mark overridden methods with @override
0 reviews · 2h to merge
#681 test: fix possibly-undefined and deprecated call sites
0 reviews · 2h to merge
#680 refactor: declare BaseAction's REPR_FIELDS and NAME as ClassVar
0 reviews · 2h to merge
#679 refactor: drop always-true truthiness checks and enable truthy-bool
0 reviews · 2h to merge
#678 chore(mypy): enable the strictness options `strict` leaves off
0 reviews · 2h to merge
How this was measured
37% of merged commits carry agent attribution — a floor, not the share; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work; reads 100 of 275 merged PRs — the rest have not been analyzed yet.
Detected: GitHub Copilot coding agent, Claude Code.
“Attributed” means a commit carried an agent’s signature — a co-author trailer, an agent commit identity, or an agent bot account. Tools that only complete code inline leave no such mark, so the other column is “rest”, not “human-written”. Full method and its limits
The badge reads this repo’s current report, so it follows the number.
Tell me when this moves
We re-read jd/tenacity weekly and email only when the number changes materially.
Read your own repos
This one is public. For a private repo, run the same read locally through your own GitHub credentials — nothing is installed and nothing is sent to us.
npx @ambera/review-taxWant this continuously on jd/tenacity — each pull request paired to the task it came from, and the work graded from its review loop rather than its diff size? Claim this repo in Forge
Browse every repo people have read · Read a different repository