Code Review Checklist for Your Team
Build a practical checklist tuned to your stack.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Build a practical code review checklist for my team. Languages and frameworks: [STACK]. Team size and review process: [TEAM_AND_PROCESS]. Common problems found in past reviews or incidents: [COMMON_PROBLEMS]. Compliance or security needs: [COMPLIANCE_NEEDS]. Return tables: 1. Checklist: Category | Check | Why it matters here | Automated by a tool? (yes, no, partly). Categories: correctness, design and readability, tests, security, performance, error handling, logging, data and migrations, compatibility, accessibility (for user interfaces), documentation. Limit to 25 checks that apply to my stack. 2. Automation: checks that should be moved to linters, type checks, formatters, static analysis, and continuous integration so humans do not spend time on them. 3. Reviewer roles: Author duties before requesting review (self-review, description, test evidence, small size) | Reviewer duties (read tests first, ask questions, distinguish blocking from non-blocking comments). 4. Comment conventions: prefixes such as "blocking:", "suggestion:", "question:", "nit:" with examples. 5. Service levels: first response time, maximum review size, and when pair review is better. 6. Pull request template. End with a calibration exercise: the team reviews one old change independently and compares findings.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.