Back to prompts
Code07.09.2026
Write a Code Review Checklist for Pull Requests
#code review#pull request#engineering#checklist
Create a practical code review checklist for this stack and team: Language / framework: [STACK] Repo type: [SERVICE, LIBRARY, MONOREPO APP] Team size: [SIZE] Risk level of changes: [LOW / MEDIUM / HIGH] Definition of done: [TEAM DOD] Common failure modes in this codebase: [BUGS OR INCIDENTS] Requirements: 1. Split the checklist into correctness, readability, tests, security, performance, and operability. 2. Include reviewer prompts (what to look for) and author prep items (what to include in the PR). 3. Call out must-block issues vs nice-to-have nits. 4. Keep it usable in under 10 minutes for a typical PR. 5. Avoid generic advice. Tie items to the stated stack and failure modes. Deliverables: 1. A PR author pre-submit checklist. 2. A reviewer checklist with severity tags (block / ask / nit). 3. A short PR description template (summary, risk, test plan, rollback).
How to use this prompt
- 1Copy the prompt using the button above.
- 2Open your AI tool (ChatGPT, Claude, Midjourney, etc.)
- 3Paste and customize any variables in the prompt.
- 4Generate your result.
Tip
Fill every placeholder before you run the prompt. Keep one clear goal per run, then refine with a follow-up if needed.
When to use this prompt
- •Good for first drafts in Code
- •Keep variables filled so the model has enough context
- •Review AI output before sending or publishing