A first-pass reviewer that reads the diff in repository context
Human review time is the scarce resource. This assistant does the first pass — the mechanical checks, the convention violations, the obvious correctness and security problems — so the human reviewer spends their attention on design and intent.
It posts comments; it does not approve or block. Merge authority stays with people.
Shortens review cycles and catches routine issues before a human spends attention on them.
Every pull request receives a first-pass review with inline comments within minutes of opening.
Run it in comment-only mode for a month and track which comment categories your team actually accepts. Turn off the categories with poor precision — a noisy bot gets muted, and then it catches nothing.
Every step in order, colour-coded by how much of it runs without a human.
Scroll to pan · use the controls to zoom, expand or export.
7 steps from trigger to result.
Review this diff for correctness. You have the surrounding repository context.
Diff:
{{diff}}
Context:
{{context}}
For each issue found:
- file and line
- what is wrong
- a concrete failure scenario: specific inputs or state that produce the wrong result
- suggested fix
Only report issues you can describe a concrete failure for. Do not report style preferences here. If the diff looks correct, say so — a clean review is a valid result.
Each tool records the role it plays and whether it is required.
ChatGPT
Primary
Required
OpenAI's conversational AI assistant for writing, research, coding, data analysis and everyday work
Claude
Supporting
Required
A safety-focused AI assistant built for long documents, careful reasoning and real work.
G
GitHub Copilot
Supporting
Optional
The default AI pair programmer — inline completion in every major editor, plus PR review.
C
Cursor
Supporting
Optional
An AI-native code editor — it reads your whole repo and edits across files, not just the cursor line.
Services this workflow connects to, and how each authenticates.
Every prompt in the workflow, in chain order. Swap the highlighted placeholders for your own values.
Review this diff for correctness. You have the surrounding repository context.
Diff:
{{diff}}
Context:
{{context}}
For each issue found:
- file and line
- what is wrong
- a concrete failure scenario: specific inputs or state that produce the wrong result
- suggested fix
Only report issues you can describe a concrete failure for. Do not report style preferences here. If the diff looks correct, say so — a clean review is a valid result.
Have these ready before you start.
Catch routine issues before a human opens the PR.
Shorter review cyclesGive first-time contributors immediate, consistent feedback.
Faster contributor onboardingRun a security pass on every change automatically.
Consistent security reviewAuthor estimates — treat them as a starting point and measure your own runs.
No reviews yet — be the first to share how this worked for you.