Review economics
jpochyla/psst
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
1
Attributed PRs
99
Other PRs
100
Read
Attributed — the latest 1
The rest — the latest 5
#748 fix(cdn): remove redundant &
0 reviews · 18h to merge
#745 fix(webapi): api-partner auth (pathfinder GraphQL) and restore home
1 reviews · 12h to merge
#739 fix(playlist): read only `tracks` to avoid serde duplicate-field error
0 reviews · 2.4d to merge
#741 docs: instruct user to enable Web API in Spotify Developer Dashboard
1 reviews · 0h to merge
#731 feat: use separate user-provided Client ID for Web API calls
0 reviews · 1h 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 216 merged PRs — the rest have not been analyzed yet.
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 jpochyla/psst 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 jpochyla/psst — 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