Code review a pull request with a checklist and severity-ranked comments
Review a diff like a senior reviewer: a checklist for correctness, security, performance and readability, comments ranked by severity and a clear approve or request-changes verdict. Designed for ChatGPT, Claude, Gemini and Microsoft Copilot. It includes 5 customizable variables and you can copy it for free in one click.
Intermediate · Code · Pending editorial review
Prompt
Act as a senior code reviewer who leaves useful, concrete and respectful comments.
Context:
- Project stack: {{stack}}
- Pull request goal: {{pr_goal}}
- Review focus: {{focus}}
- Team conventions: {{conventions}}
- Diff:
```diff
{{diff}}
```
Deliverables:
1. A 2-3 sentence summary of what the PR actually changes and whether it meets its goal.
2. A checklist applied to the diff, marking each item OK, review or N/A: correctness and edge cases, error handling, security (input, permissions, secrets), performance (N+1 queries, loops, memory), concurrency, tests, readability and naming, backward compatibility, migrations and configuration.
3. Review comments in this format: file and line, severity (blocker, major, minor, nit), problem, why it matters and a code suggestion.
4. Questions for the author when intent is unclear, instead of assuming.
5. What is done well (2-3 specific points).
6. Verdict: approve, approve with comments or request changes, with the minimum list of what must change to approve.
Constraints:
- Only comment on lines that appear in the diff; if something depends on code I have not shown, mark it [FILL IN: check outside the diff].
- Do not turn personal preferences into blockers; respect the team conventions.
- Constructive tone: describe the code, not the person.
- If the diff is incomplete or the goal is missing, ask me first.
Format: numbered sections, the checklist as a table and comments grouped by file.How to use it
Copy the diff with git diff main...your-branch or from the PR's changes view. For large PRs, review groups of related files separately and paste the useful comments straight into your Git platform.
Usage example
Stack: Django 5 and PostgreSQL · Goal: add CSV export for orders · Focus: full review · Conventions: PEP 8, tests required for services.
Sample output
Assuming the diff adds a POST /account/subscription/cancel route with its logic in SubscriptionController…
1. Summary
The PR lets customers cancel from their account and marks the subscription as cancelled, but the logic lives in the controller and nothing checks that the subscription belongs to the user.
2. Checklist (excerpt)
| Item | Status |
|---|---|
| Correctness and edge cases | Review: what if it is already cancelled? |
| Security / permissions | Review |
| Tests | Review: no service test |
| Migrations | N/A |
3. Comments
app/Http/Controllers/SubscriptionController.php L42 · blocker Any logged-in user can cancel someone else's subscription by changing the id, and the logic breaks the "no logic in controllers" convention. Suggestion:
public function cancel(Subscription $subscription, CancelSubscription $action): RedirectResponse
{
Gate::authorize('cancel', $subscription); // the policy checks ownership
$action->handle($subscription); // service with its own test
return back()->with('status', __('subscriptions.cancelled'));
}
Question for the author: does cancellation take effect immediately or at the end of the billing period? [FILL IN: check outside the diff]
6. Verdict
Request changes: a policy with a 403 test, and the logic moved to CancelSubscription…
Key facts
- Category
- Programming & development · Refactoring
- Output type
- Code
- Level
- Intermediate
- Designed for
- ChatGPT, Claude, Gemini and Microsoft Copilot
- Verified in
- Pending editorial verification
- Variables
- Project stack, PR goal, Focus, Team conventions and Diff
- Language
- English
- Price
- Free, no sign-up
- Updated
- Nov 7, 2026
Frequently asked questions
Does this replace a review by a teammate?
No. It helps you catch problems before requesting review or acts as a second opinion, but domain knowledge and team context still come from a person.
What do I do with a diff of thousands of lines?
Split it by area (model, API, UI) and review each part separately with the same goal. If you can, ask the author to break the PR into smaller changes.
What is this prompt for?
Review a diff like a senior reviewer: a checklist for correctness, security, performance and readability, comments ranked by severity and a clear approve or request-changes verdict.
Which AI tools does it work with?
It is designed for ChatGPT, Claude, Gemini and Microsoft Copilot. We have not verified it in these tools yet, so results may vary between them.
How do I customize the prompt?
Click “Customize” and fill in the variables (Project stack, PR goal, Focus, Team conventions and Diff). The text updates instantly and you can then copy it in one click. Values are stored only in your browser.
Do I need experience to use it?
It is intermediate: it helps to know the topic so you can provide good context and review the result critically.
Is this prompt free?
Yes. Every HomeCasa Prompts prompt is free, with no sign-up or subscription. You can also use them in professional projects.
Can I trust the AI output?
Treat it as a high-quality draft: always check data, figures and important claims before publishing or making decisions.