Review economics
CortexReach/memory-lancedb-pro
Read from the 100 most recently merged pull requests ·
Pull requests with attributed agent authorship took only 0.0× the review rounds of the rest.
≥6%
Attributed
a floor
6
Attributed PRs
94
Other PRs
100
Read
Attributed — the latest 5
#935 chore: single-source the smart-to-storage category map
3 reviews · 3.8d to merge
#933 chore: send the internal call label as a request header on the openai-compatible path
1 reviews · 3.8d to merge
#930 fix: skip auto-capture for internal memory sub-sessions
3 reviews · 3.8d to merge
#887 fix: fold FTS index after write threshold and on startup backlog
3 reviews · 2.3d to merge
#885 fix: await store init before retrieval routing reads hasFtsSupport
2 reviews · 2.5d to merge
The rest — the latest 5
#986 fix: exempt canonical corpus chunks from length normalization and decay
1 reviews · 15h to merge
#944 fix: attach reindex-fts and repair-summaries to the memory-pro command group
6 rounds · 10 reviews · 21.6d to merge
#941 feat: add a batch utility mode to admission control
1 round · 2 reviews · 20.8d to merge
#973 fix(reflection): keep caller-requested aborts out of the transient retry class
1 reviews · 4.7d to merge
#934 fix: gate the auto-capture regex fallback behind smart extraction and admission
12 rounds · 14 reviews · 20.6d to merge
Against other teams
Attributed work here takes 0.0× the review rounds of the rest — below the 0.6× median across 2353 published teams.
Higher than 11% of the 2353 published reports. See the distribution
How this was measured
6% 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; 36 PRs came off an agent branch with no commit attribution, so the real share runs higher; reads 100 of 295 merged PRs — the rest have not been analyzed yet.
Detected: Claude Code, OpenAI Codex.
“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 CortexReach/memory-lancedb-pro 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 CortexReach/memory-lancedb-pro — 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