You decide when a pull request gets reviewed.
You comment @boson review on a pull request. Boson reads that diff once, traces the changed lines through their callers, and quotes exactly where it breaks. Ask again next time you want another pass.
- GitHub issue
- Jira ticket
- Confluence page
- Code symbol
What happens after you comment
- Step 1 of 4
You ask for a review
Comment "@boson review" on an open pull request. That's the whole setup, no config file to add to your repo.
- Step 2 of 4
Deterministic checks run first
Boson checks the diff against the merge-base commit: is the line actually changed, does the snippet match, what does blame say, has this already been flagged. A model never sees a diff that fails these.
- Step 3 of 4
What's left gets read for a reason to reject it
Boson reads the change the way a reviewer looking to reject it would, following each line through its callers until it lands on a concrete, reproducible outcome.
- Step 4 of 4
One comment, evidence attached
Boson quotes the code and the path from that line to the failure it causes. Reading the comment is enough to check the finding yourself.
Credits, pooled at the organization
One credit pays for one review. Every review gets the same depth, there is no faster or slower tier and nothing multiplies the cost. The balance sits at the organization rather than at any one developer's seat, and it only drains when someone actually asks for a review.
| Plan | Free | Pro | Teams | Enterprise |
|---|---|---|---|---|
| Price | $0No card required | $30per month | $100per month | CustomContact sales |
| Credits / month | 10 | 50 | 250 | Custom volume |
| Cost per credit | Included | $0.60 | $0.40 | Custom |
| Overage | Not available | Opt-in, $1.00 / credit | Opt-in, $1.00 / credit | Custom terms |
| Start free | Get started | Get started | Talk to us |
Pro and Teams are live ahead of the full cost-per-review measurement, by the owner's own call: the price is set to hold even if that measurement lands high, not the other way round. Overage past your included credits is opt-in and stays off until you set a spending cap yourself, so a busy month never bills you a surprise.
What you can verify yourself
We haven't run enough reviews yet to publish an accuracy number we'd stand behind, so here are none. Pull up an actual comment Boson posts and check each line below against it.
- Every finding quotes the exact code and traces a path from that line to a concrete, user-visible failure.
- Deterministic checks run before any model sees the diff: line in diff, snippet match, blame, duplicate detection.
- It's a comment. Nothing else on the pull request changes because Boson ran.
Try it on your next pull request.
Install the GitHub App on a repo, then comment @boson review the next time a pull request needs someone hunting for the way it breaks. No config file to write.