Review economics
jasontang-ai/Context-Engineering
Read from the 15 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥21%
Attributed
a floor
2
Attributed PRs
13
Other PRs
15
Read
Attributed — the latest 2
The rest — the latest 5
#31 Fix: convert 02_expand_context.py from notebook-style to valid Python script
0 reviews · 49.7d to merge
#25 Update 01_long_context_processing.md
0 reviews · 15.7d to merge
#22 Fix stale reference in README.md, make quickstart clickable
0 reviews · 9h to merge
#21 Added missing pointer between step 04 and 05 of the foundation series.
0 reviews · 20h to merge
#20 Fixing simple reference mistake
0 reviews · 21h to merge
How this was measured
21% 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.
Detected: Claude Code, 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 jasontang-ai/Context-Engineering 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 jasontang-ai/Context-Engineering — 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