Code Review Comments
Constructive code review feedback templates for common issues.
Updated Summary
Hi {{cursor}},
Following up on our recent conversation about updated summary.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
Please let me know if you have any questions or if there is anything else I can help with.
Best regardsRevised Alert
Revised Alert
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of revised alert]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]Initial Note
Hi {{cursor}},
Quick update on initial note:
[Key information]
Let me know if you have any questions.
BestFollow-Up Memo
Follow-Up Memo
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of follow-up memo]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Standard Version
Hi {{cursor}},
I wanted to bring something important to your attention regarding standard version.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
Please let me know if you have any questions or if there is anything else I can help with.
Best regardsFormal Response
Formal Response
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of formal response]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]Friendly Update
Hi {{cursor}},
Quick update on friendly update:
[Key information]
Let me know if you have any questions.
BestBrief Template
Brief Template
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of brief template]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Detailed Notification
Hi {{cursor}},
Following up on our recent conversation about detailed notification.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
I look forward to hearing from you. Feel free to reply to this message or schedule a call.
Best regardsProfessional Request
Professional Request
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of professional request]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]Advanced Format
Hi {{cursor}},
Quick update on advanced format:
[Key information]
Let me know if you have any questions.
BestUrgent Notice
Urgent Notice
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of urgent notice]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]When to use this template
- Recurring feedback (naming, error handling, missing tests) that you write the same comment for every week. Save it once.
- Approval comment with specific praise so the contributor knows what worked and the comment isn't just a stamp.
- Request-changes comment that's firm but constructive, with a path to resolution.
Customize for your workflow
- Frame feedback as questions when you're not sure. 'Could this leak memory under X?' invites discussion. 'This leaks memory' invites defensiveness.
- Mark blocking vs nit comments clearly. A 'nit:' prefix saves the contributor 30 minutes of debating cosmetic preferences.
Common questions
How long should code review comments be?
Short. If your comment requires three paragraphs, schedule a 15-minute pairing session instead. Long comments get skimmed.
Should I use AI to write code review comments?
For generating feedback drafts, sure. Always read what it produced before posting — AI tends to over-acknowledge and bury the actual point.
Related reading
More Software Development Templates
Pull Request Templates
PR description formats with context, testing, and review guidance.
9 snippetsBug Report Templates
Structured bug report formats with reproduction steps and environment details.
8 snippetsTechnical Documentation
API documentation, README templates, and architecture decision records.
10 snippetsGit Commit Messages
Conventional commit message templates for features, fixes, and refactors.
11 snippetsRelease Notes Templates
Changelog and release announcement formats for software updates.
8 snippetsCode Comment Standards
Documentation comment templates for functions, classes, and modules.
9 snippetsTechnical RFC Templates
Request for comments templates for proposing technical changes.
8 snippetsOn-Call Handoff Templates
On-call rotation handoff notes and incident status templates.
10 snippetsUse these snippets in TypeFire
Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.