Pull Request Templates
PR description formats with context, testing, and review guidance.
Urgent Summary
Hi {{cursor}},
I wanted to bring something important to your attention regarding urgent 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.
Thank you for your time and attention. I will follow up if I do not hear back by [date].
Best regardsRoutine Alert
Routine Alert
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of routine 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]Personalized Note
Hi {{cursor}},
Quick update on personalized note:
[Key information]
Let me know if you have any questions.
BestFinal Memo
Final Memo
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of final memo]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Updated Version
Hi {{cursor}},
Thank you for reaching out regarding updated 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.
I look forward to hearing from you. Feel free to reply to this message or schedule a call.
Best regardsRevised Response
Revised Response
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of revised 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]Initial Update
Hi {{cursor}},
Quick update on initial update:
[Key information]
Let me know if you have any questions.
BestFollow-Up Template
Follow-Up Template
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of follow-up template]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Standard Notification
Hi {{cursor}},
I am writing to update you on standard 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 regardsWhen to use this template
- Feature PR with sections for what changed, why, and how to verify. Same structure across the team makes reviews faster.
- Bug fix PR linking the issue, explaining the root cause, and listing the test case that now catches it.
- Refactor or chore PR where you want to make clear nothing user-facing should change, plus what risk the refactor introduces.
Customize for your workflow
- Match your team's actual review checklist. If you require Linear/Jira ticket links, the template should include a placeholder with the right link format.
- Add a 'Testing' section even for trivial PRs. Forces you to think about whether you actually verified the change.
Common questions
How long should a PR description be?
Long enough to review without context-switching to the issue tracker. Three paragraphs usually. Even longer for risky changes.
Do PR templates work in GitHub?
Yes — drop the markdown into `.github/pull_request_template.md` in your repo. Each new PR pre-populates with the template. TypeFire snippets work alongside this for further customization.
Related reading
More Software Development Templates
Code Review Comments
Constructive code review feedback templates for common issues.
12 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.