Review economics
Ebazhanov/linkedin-skill-assessments-quizzes
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.
—
Attributed
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#7238 docs: add community API & web demo link
1 reviews · 4h to merge
#7258 docs: add Jefsky as a contributor for design, and code
0 reviews · 0h to merge
#7257 fix: correct spelling typo 'Javascipt' to 'JavaScript'
1 reviews · 1h to merge
#7250 Fix IT Ops answers Q18, Q20, Q31, Q43, Q51, Q52 (#3884)
1 round · 7 reviews · 2.6d to merge
#7248 Fix Q6 Go import statement: correct github.com/gin-gonic/gin
1 reviews · 16h to merge
How this was measured
No commit in this window carries agent attribution, so there is no AI-authored share to read here — which is not evidence there is none; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work; reads 100 of 5769 merged PRs — the rest have not been analyzed yet.
“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 Ebazhanov/linkedin-skill-assessments-quizzes 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 Ebazhanov/linkedin-skill-assessments-quizzes — 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