Dev Tools · Startup idea
AI code review: the GitHub Action that doesn't ship junk PRs
Every AI code-review tool currently spams the PR with low-signal comments. The product that wins is the one that ships <3 comments per PR and is right >85% of the time.
Why now
GitHub Copilot Review, CodeRabbit, Cursor's reviewer, and a dozen others are racing. None of them solved the signal-to-noise problem. The team that fine-tunes a small reviewer model on a per-repo basis beats the generic ones.
The idea you could build today
GitHub App that listens to PRs. On open, run the diff through a 2-stage review: cheap model proposes, expensive model filters. Comment only what passes the filter. Train a per-repo classifier on which comments the team accepted vs. dismissed.
Build stack
- ·GitHub App (Probot)
- ·Anthropic Claude or GPT-class for the diff review
- ·Small classifier model fine-tuned on accept/dismiss
- ·Postgres for the per-repo feedback graph
The three repos already trying
Pulled live from our current-period signal index.
No repos in the current period have crossed our minimum-volume + sector match for this idea. That can mean two things, the niche is too new for public GitHub signal to show up yet, or the buildable wedge is genuinely greenfield. Either way, watch this page; matches refresh weekly.
Matched against the current-period startup signal panel (developer-tools, ai-ml). Rankings shift weekly as the underlying GitHub activity moves. Read the methodology.
The seed-round pattern hiding in the trendline
OSS code-review repos with sudden contributor surges around "per-repo training" or "comment classifier" modules are the seed-round leads.
Frequently asked
What about CodeRabbit?+
Leader of the current generation. The bet is the next generation, per-repo fine-tuning beats generic-prompt fanfic on signal quality.
Use the signal, not just the idea
Watch this idea live, every week.
The repos above re-rank automatically as commit velocity, contributor growth, and new-repo creation move. Want the data feed for this idea wired into your own stack? The MCP server exposes every signal as a tool any agent host can query.
Related ideas
Updated 2026-08-25. The framing is editorial; the “three repos already trying” slot is generated from the live signal panel. Anonymity rule: we name public GitHub orgs, never individual founders or stealth teams.