💻Software Development

Git Commit Messages

Conventional commit message templates for features, fixes, and refactors.

11 snippets included|Free to download|Works with TypeFire for macOS
Download TypeFire for macOS
zsdgcm1

Urgent Memo

Hi {{cursor}},

I wanted to bring something important to your attention regarding urgent memo.

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 regards
zsdgcm2

Routine Version

Routine Version

Date: {{date}}
Prepared by: {{cursor}}

Summary:
[Brief overview of routine version]

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]
zsdgcm3

Personalized Response

Hi {{cursor}},

Quick update on personalized response:

[Key information]

Let me know if you have any questions.

Best
zsdgcm4

Final Update

Final Update

Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}

Description:
[Detailed description of final update]

Key Points:
- [Point 1]
- [Point 2]
- [Point 3]

Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]

Notes:
[Additional information]
zsdgcm5

Updated Template

Hi {{cursor}},

Following up on our recent conversation about updated template.

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 am happy to discuss this further at your convenience. Please do not hesitate to reach out if you need anything else.

Best regards
zsdgcm6

Revised Notification

Revised Notification

Date: {{date}}
Prepared by: {{cursor}}

Summary:
[Brief overview of revised notification]

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]
zsdgcm7

Initial Request

Hi {{cursor}},

Quick update on initial request:

[Key information]

Let me know if you have any questions.

Best
zsdgcm8

Follow-Up Summary

Follow-Up Summary

Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}

Description:
[Detailed description of follow-up summary]

Key Points:
- [Point 1]
- [Point 2]
- [Point 3]

Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]

Notes:
[Additional information]
zsdgcm9

Standard Alert

Hi {{cursor}},

I am writing to update you on standard alert.

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 regards
zsdgcm10

Formal Note

Formal Note

Date: {{date}}
Prepared by: {{cursor}}

Summary:
[Brief overview of formal note]

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]
zsdgcm11

Brief Guide

Hi {{cursor}},

Quick update on brief guide:

[Key information]

Let me know if you have any questions.

Best

When to use this template

Customize for your workflow

Common questions

Should commit messages be one line or multi-line?

One-line subject (under 72 chars) plus a blank line plus a body when needed. Most history-viewing tools rely on this convention.

Why not just use 'WIP' commits?

WIP commits make `git log` useless and break bisecting when you need to find which change broke a test. Squash before merging if the intermediate commits don't matter.

Related reading

More Software Development Templates

Use these snippets in TypeFire

Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.

Get TypeFire Free