Pull request review
When a pull request opens, a reviewer reads the diff from your repository, runs a correctness, security, and standards pass, and drafts specific inline comments plus a verdict for you to approve before anything is posted.
Saves you ~2.2 h / run
How it works
- Trigger
- When you start the “Code review” workflow.
- Job
- Read the diff, run the review and security passes.
- Outcome
- A prioritized code review with evidence and draft comments.
What it installs
Agents 2
-
Reviewer Agent
Reads the PR diff, runs the review checklist and security pass, and drafts line-anchored comments and a verdict for approval.
-
Pull request review Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Pull request review quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Code review
Read the diff, run the review and security passes, self-check for false positives, then draft comments and a verdict for approval.
Goals 1
-
Every PR reviewed
Keep a substantive review on every pull request so nothing merges unexamined. Success looks like: Each opened pull request receives an approved, line-anchored review with a clear verdict before it merges, and no PR merges without one.
Skills 3
-
code-review
Thorough correctness, performance, design, and test-coverage review with specific, actionable, line-anchored comments and a clear verdict; approve on minor issues, escalate schema/API/security changes. Adapted from getsentry/skills/code-review.
-
security-review
Exploitability-first security pass reporting only high-confidence findings: trace attacker-controlled input to a sink, skip framework-mitigated and server-controlled patterns, classify by severity, and report the input path plus fix. Adapted from getsentry/skills/security-review.
-
requesting-code-review
Frame review feedback so it is easy to act on: classify each finding Critical/Important/Minor, fix-then-proceed by class, give the reviewer only the work product not the session history, and review early and often. Adapted from obra/superpowers/requesting-code-review.
Requirements
- Connected repository — The agent reads the pull request diff, the changed files, and surrounding code from your connected repository. Until repository access is connected, it reviews from the diff and files supplied as attachments.
Setup guide
How to Automate Pull Request Reviews
A practical guide to reviewing pull requests with an agent: a correctness and security checklist, severity-classified comments, and approval before posting.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.