Write conventional git commit messages with subject, body, and trailers.
npx skills add https://github.com/mattschwartz/systemos --skill git-commit-mattschwartz
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/mattschwartz/systemos/tree/main/.claude/skills/git-commit Command: npx skills add https://github.com/mattschwartz/systemos --skill git-commit-mattschwartz
Writing clear, consistent git commit messages is essential for future readers to understand why changes were made and how they relate to the project history. This guide teaches a disciplined approach to formatting subjects, composing bodies, and applying trailers to attribute authorship.
Draft a clear subject line and an informative body for your next commit.
High-intent search queries and answers about installing and using this skill.
To write a conventional git commit message, format the subject line as type(scope): short description, then use the body to explain why the change was made and what technical details were modified. This structure clarifies intent for features, fixes, and refactors.
The body of a git commit message should explain the why and scope of the change, providing technical context beyond the diff. Detailing why the modification was necessary helps future readers understand project history and improves bisectability.
To add a Co-authored-by trailer for shared git commits, append the trailer at the end of the commit message body to attribute authorship to multiple contributors. This acknowledges collaboration and links shared work during pull request reviews.
The best way to format git commit subjects for pull request reviews is using the type(scope): description format. Keeping the subject concise and descriptive ensures changelog accuracy and communicates the commit intent clearly to reviewers.
You need to use conventional commit formats in version control workflows whenever you want to improve changelog accuracy and bisectability. Applying structured subject, body, and trailer usage to feature work and bug fixes communicates intent to future readers.
TheDecipheristGenerate conventional commit messages from git diffs using the Conventional Commits format.
haowang020110Automate Git operations for .gitignore, grouped commits, and remote sync.
beratcelik1Generate conventional commit messages from staged or unstaged Git diffs.
Tonybleything76Generate changelog entries from Git commit history using Conventional Commits.
