Review economics
markzhai/AndroidPerformanceMonitor
Read from the 24 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
24
Other PRs
24
Read
The rest — the latest 5
#107 [fix]Fix the error of writing logs on some api level of Android devic…
0 reviews · 0h to merge
#97 Update README_cn
0 reviews · 0h to merge
#86 支持开发者设置：代码调试模式下是否应该停止检测
0 reviews · 3h to merge
#82 修正displayNotification 为false ,onBlock不回调的问题
0 reviews · 0h to merge
#76 解决分享后删除按钮失灵的bug
0 reviews · 46h 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.
“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 markzhai/AndroidPerformanceMonitor 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 markzhai/AndroidPerformanceMonitor — 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