Git Commit Templates Library
Consistent commit messages, however you work. Explore templates for Tower and Git, plus skills that teach your coding agent the same conventions.
Every template works in Tower, on the Git command line, and with coding agents. New here? Start with Simple Commit or Conventional Commits.
General Formats
—Everyday structures for any commit- Simple Commit Good starting pointA concise subject line with an optional explanatory body.Tower suggestion→
<Summarize the change in imperative mood, about 50 characters> - Conventional Commits Good starting pointStructured type, scope, description, body, and footers.published convention→
<type>(<optional scope>): <description> - GitmojiAn emoji prefix that makes the intent of each change easy to scan.published convention→
<gitmoji> <Summarize the change> - Subsystem PrefixThe affected area as a prefix, followed by a short summary.published convention→
<area>: <summarize the change in imperative mood> - Detailed ChangeWhat changed, why, and how it was verified.Tower suggestion→
<Summarize the change in imperative mood>
Specific Situations
—Capture what matters for a particular kind of change- Bug FixProblem, cause, fix, and verification.Tower suggestion→
Fix <the observable problem> - Breaking ChangeCompatibility impact and migration guidance.Tower suggestion→
<Summarize the change in imperative mood> - Issue-Linked CommitChange summary and relevant issue references.Tower suggestion→
<Summarize the change in imperative mood> - RevertReverted commit, reason, and consequences.Tower suggestion→
Revert "<subject of the reverted commit>" - Performance ImprovementChange, measurement conditions, and before/after results.Tower suggestion→
<Summarize the improvement in imperative mood>
Published conventions follow an external guide or specification. Tower suggestions are adaptable starting points. Change them to fit your team.