Review economics
666ghj/MiroFish
Read from the 26 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥1%
Attributed
a floor
1
Attributed PRs
25
Other PRs
26
Read
Attributed — the latest 1
The rest — the latest 5
#755 chore: update Star History
0 reviews · 0h to merge
#754 fix: submit Star History updates as pull requests
0 reviews · 0h to merge
#752 Fix automated Star History updates on protected main
0 reviews · 0h to merge
#742 fix: harden ontology JSON generation across LLM providers
0 reviews · 0h to merge
#740 fix: modernize Zep Cloud integration and dependency security
0 reviews · 0h to merge
How this was measured
1% 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; 4 PRs came off an agent branch with no commit attribution, so the real share runs higher.
Detected: OpenAI Codex, Cursor agent.
“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 666ghj/MiroFish 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 666ghj/MiroFish — 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