Starter
Try AI PR review.
- 2 reviewers
- Code Review
- Security Review
- 3 seats included
- 15,000 credits to start, then 5,000/mo
- About 70 reviews to start, then about 25 a month
- Unlimited repos
Before you ask for review, check six things: one small change, a description that says what and why, a test that fails without the change, every file that changes with it, no secrets, and docs that still match.
What lands on your pull request · Code Review
billing/checkout.ts:42 · A timed-out response can charge the order twice- await payments.charge(order);+ await payments.charge(order, {+ idempotencyKey: order.id,+ });
The fourth matters most. When two AI readers graded 267 IonWarp findings, nearly all from 24 to 29 September 2026, 12 of the 17 real merge blockers were a pull request that changed one thing and missed a test, a migration list, a config value or a second read path that had to change with it.
Split a refactor from a behavior change, and a rename from both. A short diff gets read line by line; a long one gets skimmed. When one change builds on another, stacked pull requests keep each one small.
What changes, why, and how to check it. Write Closes #123 to link the issue, and GitHub closes it when the pull request merges into the default branch.[1]
If you are not sure it does, run it once against the old code.
Search for the callers of anything you renamed, removed or retyped, and for the tests, migrations, configs and docs that name it.
Code ReviewOn Starter, Pro and Max
No token, key or password in the code, a log line, an error message or the client bundle.
Security ReviewOn Starter, Pro and Max
The README, comments and agent instructions such as CLAUDE.md or AGENTS.md that this change made wrong.
Docs ReviewOn Pro and Max
## Summary
<!-- What this changes, in one or two sentences. Closes #123 -->
## Why
<!-- The problem or decision behind the change. -->
## How to test
<!-- The command to run or the steps to click, and what the reviewer should see. -->
## Risk and rollback
<!-- What could break, who it affects, and how to undo it. -->
## Screenshots
<!-- Before and after, for any change a user can see. -->
## Checklist
- [ ] A test covers the change
- [ ] Callers of anything renamed, removed or retyped are updated
- [ ] Docs that this change made wrong are updated
- [ ] No secrets in code, logs or the client bundleSave it as .github/pull_request_template.md. GitHub fills each new pull request with it once it is on the default branch.[2] A CODEOWNERS file in the same folder requests a review from each path owner automatically.
One workspace price with seats included. Credits pool across your team. Unlimited repos on every plan.
Try AI PR review.
Get AI PR review right from day 1.
Scale AI PR review.
Custom reviewers + credits · GitHub Enterprise · SSO/SAML + audit logs · Custom security review + SLA
Name it pull_request_template.md and put it in the repository root, the docs folder or the .github folder. For several templates, add a PULL_REQUEST_TEMPLATE folder and pick one with the template query parameter. Templates apply once they are merged into the default branch.
What changes, why, how to test it, and what could break. Link the issue it closes, and add screenshots for anything a user can see.
Write Closes #123 in the description, or Fixes or Resolves. GitHub closes the issue when the pull request merges into the default branch.
No. The pull request checklist is the author's, done before asking for review. The code review checklist is the reviewer's: correctness, what the change breaks elsewhere, security and design. Our guide What is code review? lists it.