Review economics
microsoft/VFSForGit
Read from the 100 most recently merged pull requests ·
Pull requests with attributed agent authorship took 1.6× the reviews submitted of the rest.
≥9%
Attributed
a floor
3
Attributed PRs
97
Other PRs
100
Read
Attributed — the latest 3
The rest — the latest 5
#2071 Split blob-hydration and directory-enumeration failure telemetry by cause
1 reviews · 16.2d to merge
#2073 Update default Microsoft Git version to v2.55.0.vfs.0.3
1 reviews · 1h to merge
#2072 Bump actions/setup-dotnet from 5 to 6
1 reviews · 0h to merge
#2068 ci: run build.yaml on vnext
1 reviews · 4.9d to merge
#2069 Update default Microsoft Git version to v2.54.0.vfs.0.5
1 reviews · 0h to merge
How this was measured
9% 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 1001 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 microsoft/VFSForGit 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 microsoft/VFSForGit — 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