GitHub Code Review Checklist and Comment Templates
Give reviewers a consistent checklist and kind comment patterns.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Create a code review guide for [TEAM]. Languages and frameworks: [STACK]. Typical change types: [CHANGE_TYPES]. Problems in past reviews (slow, nitpicking, missed bugs): [PROBLEMS]. Review time expectation: [REVIEW_TIME]. Write a one-page checklist: understanding the change, correctness and edge cases, tests, readability, security basics (input handling, secrets, permissions, dependencies), performance, documentation, and operational concerns (logging, rollback). Define comment labels such as blocking, suggestion and question, with a template for each, including how to ask politely for a change, praise good work, and disagree. Review the code, not the person, and separate preference from requirement. Mention that automated checks should handle style so humans do not. Add rules for authors (describe the change, run tests, self-review first), a pull request size guideline with an approach for large changes, and rules for response times and resolving disagreement. Give three comments before and after rewriting for tone, using invented code. Keep the tone friendly and direct. If the checklist is longer than one page, say which items are essential and which only apply to large or risky changes.
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.