Code review that reads the whole repo
Kestrel reviews every pull request with your entire codebase in context, and only speaks up when a change breaks something the diff can’t show.
Floats lose the cent here: a 1,000.005 refund rounds to 1,000.00. toCents() in billing/cents.ts already works in integer cents.
REVIEW
CONTEXT IT USED
TESTS
Your diff touched 3 files.
Kestrel read 2,184.
Twenty-three nits, or the one bug.
Most review bots comment on everything they can see. Kestrel stays quiet until something is wrong, then tells you where the fix already lives.
A typical review bot
23 commentsKestrel
1 commentFloats lose the cent here. toCents() in billing/cents.ts already works in integer cents.
Ten minutes to set up. Then it just reviews.
One app on your repositories, one read of the codebase, then a comment only when a change breaks something.
Install the app on your repos.
One GitHub or GitLab app. Pick the repositories; Kestrel asks only for what a reviewer needs.
- No CI changes
- No config file to start
It reads the whole repository once.
Kestrel maps every caller, import and test, then keeps the map current as you merge.
- A mid-size repo maps in about four minutes
- Code is deleted when the review ends
It reviews every pull request.
Comments land in the pull request like a teammate’s. Blocking issues fail one check; notes never do.
- Under a minute for most pull requests
- Reply to it, and it answers in the thread
issueInvoice() still passes floats. This change fixes refunds but leaves invoices a cent off.
1.4 comments per pull request, across forty teams.
It caught a timezone bug in a file nobody had opened in two years. That one comment paid for the beta.
The first review bot we turned on that people kept on. It doesn’t talk unless it has to.
Our seniors were the only ones who knew where the money helpers lived. Now every pull request gets that review.
SampleSample quotes and numbers. Replace them with your own before you publish.
We let teams in a wave at a time.
Each wave gets a direct line to the people building it. Places go in the order people join.
Wave 1
Forty teams on TypeScript and Go, reviewing real pull requests every day.
Wave 2
Python and Ruby join, and GitLab support lands. This is the list you’re joining.
Public
Beta teams keep their price for a year.
Before you join
Anything else goes to the team directly: reply to the confirmation e-mail.
Does my code leave our servers?
Code is read in an isolated workspace, used for the review and deleted when it ends. Nothing is kept to train a model.
Which languages work today?
TypeScript, JavaScript and Go in wave 1. Python and Ruby arrive with wave 2.
What does it cost?
Nothing during the beta. We’ll publish pricing before the public launch, and beta teams keep their price for a year.
Does it replace human review?
No. It catches what a reviewer can’t see from the diff, so people can spend their review on design and intent.
How many e-mails will I get?
One to confirm, one when your place opens. No newsletter.
Get on the list for wave 2.
Places open in the order people join. One e-mail when yours is ready.