Review economics
TableProApp/TablePro
Read from the 100 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
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#2023 fix(mysql): report generated columns so SQL export excludes them
1 reviews · 3h to merge
#2025 fix(editor): keep Cmd+Delete and Option+Delete in the editor instead of the data grid (#2022)
0 reviews · 0h to merge
#2024 fix(datagrid): stop every second refresh from cancelling its own query (#2021)
0 reviews · 0h to merge
#2020 feat: note the Claude subscription tradeoffs and translate the remaining strings
0 reviews · 0h to merge
#2017 fix(datagrid): draw the header chrome to fit a comment line
0 reviews · 9h 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; reads 100 of 1285 merged PRs — the rest have not been analyzed yet.
Detected: 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 TableProApp/TablePro 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 TableProApp/TablePro — 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