Over the past few months, we've been completely rebuilding cubic's AI review engine. Today we're excited to announce cubic 2.0, the most accurate AI code reviewer available. cubic helps teams read, trust, and merge AI-generated code in real repos. It is optimized for accuracy and low noise, and it goes beyond PR comments with a CLI, AI docs, and PR description updates. Used by 100+ orgs including Cal.com, n8n, Granola, and Linux Foundation projects.
If you’ve tried AI code review tools before, you’ve probably seen both failure modes:
1. they miss the important stuff
2. they comment so much that you stop reading
We built cubic because review is now the bottleneck. AI made it easy to produce code. It did not make it easy to trust a big diff in a complex repo.
Over the last few months we’ve been iterating hard on the engine, and the change is big enough that we’re calling it cubic 2.0. It’s faster, more accurate, and noticeably less noisy than it was a few months ago.
The other thing we learned is that “a GitHub bot that comments on PRs” is not enough anymore. Review is a workflow, not a feature, so we built the pieces around it too:
- incremental checks on every push
- PR descriptions that stay accurate
- wiki docs that stay in sync
- `cubic.yaml` for config-as-code
- and a CLI so you can run review before you push
If you try it, I’d love blunt feedback:
- What did it catch that you actually cared about?
- What should it stop commenting on?
I’ll be here in the comments!
About cubic 2.0 on Product Hunt
“Code reviews for the AI era”
cubic 2.0 launched on Product Hunt on January 12th, 2026 and earned 143 upvotes and 8 comments, placing #8 on the daily leaderboard. Over the past few months, we've been completely rebuilding cubic's AI review engine. Today we're excited to announce cubic 2.0, the most accurate AI code reviewer available. cubic helps teams read, trust, and merge AI-generated code in real repos. It is optimized for accuracy and low noise, and it goes beyond PR comments with a CLI, AI docs, and PR description updates. Used by 100+ orgs including Cal.com, n8n, Granola, and Linux Foundation projects.
On the analytics side, cubic 2.0 competes within Software Engineering, Developer Tools and Artificial Intelligence — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how cubic 2.0 performed against the three products that launched closest to it on the same day.
Who hunted cubic 2.0?
cubic 2.0 was hunted by Garry Tan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Garry Tan
Hey Hunters, I’m Paul, the founder of cubic.
If you’ve tried AI code review tools before, you’ve probably seen both failure modes:
1. they miss the important stuff
2. they comment so much that you stop reading
We built cubic because review is now the bottleneck. AI made it easy to produce code. It did not make it easy to trust a big diff in a complex repo.
Over the last few months we’ve been iterating hard on the engine, and the change is big enough that we’re calling it cubic 2.0. It’s faster, more accurate, and noticeably less noisy than it was a few months ago.
The other thing we learned is that “a GitHub bot that comments on PRs” is not enough anymore. Review is a workflow, not a feature, so we built the pieces around it too:
- incremental checks on every push
- PR descriptions that stay accurate
- wiki docs that stay in sync
- `cubic.yaml` for config-as-code
- and a CLI so you can run review before you push
If you try it, I’d love blunt feedback:
- What did it catch that you actually cared about?
- What should it stop commenting on?
I’ll be here in the comments!