How it works
Code analyzed
The agent reads the diff, understands the context of the changes, and evaluates them against your coding standards.
Set up automated PR reviews
1. Connect your source control
Navigate to the Integrations page and connect GitHub, GitLab, or Bitbucket.2. Create an automation
Go to Automations in your dashboard and use the PR Review template, or create one from scratch. Trigger: PR opened / PR updated (webhook from GitHub, GitLab, or Bitbucket) Example instructions:3. Customize with rule files
Add rule files to your repo so the reviewer knows your team’s conventions: naming patterns, test requirements, forbidden patterns, and more.What gets checked (depends on your instructions)
| Category | Examples |
|---|---|
| Correctness | Logic errors, off-by-one bugs, null handling |
| Security | SQL injection, XSS, hardcoded secrets |
| Performance | N+1 queries, unnecessary allocations, missing indexes |
| Style | Naming conventions, formatting, import order |
| Testing | Missing tests, untested edge cases |
Best practices
- Add rule files: The more context the reviewer has about your standards, the better the review.
- Start with one repo: Test the review quality on a single repo before rolling out to all.
- Combine with human review: Use automated reviews to catch the obvious stuff so human reviewers can focus on architecture and design.