Review economics
OpenSPG/KAG
Read from the 99 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥0%
Attributed
a floor
2
Attributed PRs
97
Other PRs
99
Read
Attributed — the latest 2
The rest — the latest 5
#736 Fix McpExecutor kag_project_config initialization for MCP HTTP store_…
2 reviews · 18.5d to merge
#652 fix(solver): fix naive rag and split
2 reviews · 19.9d to merge
#642 fix(solver): fix bug for server params
2 reviews · 5.9d to merge
#640 feat(solver): support kag thinker
2 reviews · 1h to merge
#628 fix(builder): remove KAG_PROJECT_CONF
2 reviews · 6.0d to merge
How this was measured
0% 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 99 of 231 merged PRs — the rest have not been analyzed yet.
Detected: Google Jules.
“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 OpenSPG/KAG 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 OpenSPG/KAG — 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