Generate conventional Git commit messages with subject and body rules.
npx skills add https://github.com/mikker/dotfiles --skill commit-mikker
Please help me install this Agent Skill. Skill: commit Source: https://github.com/mikker/dotfiles/tree/main/agents.symlink/skills/commit Command: npx skills add https://github.com/mikker/dotfiles --skill commit-mikker
This Skill provides a structured guideline to write clear, conventional Git commit messages, improving traceability and collaboration across development teams.
Generate a concise, conventional Git commit message that follows subject/body rules and references related issues when applicable.
High-intent search queries and answers about installing and using this skill.
A conventional Git commit message uses a concise subject line starting with a capitalized imperative verb. Enforce subject line capitalization and maximum length, separate the subject and body with a blank line, and use an optional body to explain what and why.
The maximum length for a Git commit subject line is enforced to keep messages concise. A capitalized imperative verb begins the subject, which is followed by a blank line before the optional body wraps at 72 characters to explain what and why.
To format a Git commit body for multiple changes, use bullet points to detail each modification. The body is separated from the subject by a blank line, wrapped to 72 characters, and explains what changed and why the changes were made.
To reference issues or PRs in a Git commit message, include the references within the message structure. The commit message supports referencing issues and PRs when relevant, alongside a capitalized imperative subject line and an optional body explaining what and why.
You do not need a specific Git workflow to generate conventional commit messages. The guidelines apply to software development workflows to generate or validate subject and body lines for single commits or grouped changes without requiring special dependencies.
Imperative mood in Git commit subject lines provides clear, direct instructions about what the commit does. Enforcing a capitalized imperative verb ensures consistency, improving traceability and collaboration across software development teams.
maslennikov-igGenerate conventional commit messages from git diffs.
MelvynxGenerate conventional commit messages and push changes to the repository.
mrleeioFormat git commit messages according to the Conventional Commits standard.
ArabelaTsoGenerate Markdown changelogs from git commit history with conventional commits.
