Review economics
ronitsingh10/FineTune
Read from the 25 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥2%
Attributed
a floor
0
Attributed PRs
25
Other PRs
25
Read
The rest — the latest 5
#224 feat(audio): add loudness compensation and equalization based on ISO 226 contours
0 reviews · 3.3d to merge
#362 DDC: send VCP writes twice
0 reviews · 4.6d to merge
#361 DDC: stop crash on volume change with DDC output
0 reviews · 4.3d to merge
#330 [Codex] Add device-aware menu bar icon style
0 reviews · 7.8d to merge
#327 fix(audio): honour aggregate device channel assignment (e.g. stereo on 3/4)
0 reviews · 11.5d to merge
How this was measured
2% 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.
Detected: 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 ronitsingh10/FineTune 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 ronitsingh10/FineTune — 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