Generate conventional commit messages with type, kebab-case scope, and imperative subject.
npx skills add https://github.com/ajbmachon/ajbm-skills --skill commit-ajbmachon
Please help me install this Agent Skill. Skill: commit Source: https://github.com/ajbmachon/ajbm-skills/tree/main/.claude/skills/commit Command: npx skills add https://github.com/ajbmachon/ajbm-skills --skill commit-ajbmachon
This Skill removes the friction and inconsistency of writing commit messages by guiding you to produce Conventional Commits with a correct type, required scope, and a clear subject line.
type(scope): subject with scope enforced in kebab-case and subject rules (imperative, max length, no trailing period).Tell Claude to write a Conventional Commit message for the staged changes, including a type, required kebab-case scope, subject line, and (if needed) a clear body with HOW/WHY and a reference to the task or requirement.
High-intent search queries and answers about installing and using this skill.
To generate conventional commit messages, provide the staged changes to get output formatted as `type(scope): subject` with a required kebab-case scope and an imperative subject line. This ensures consistent software maintenance history across your repository.
The correct format for a conventional commit requires a type, a kebab-case scope, and a concise imperative subject line with no trailing period. This structure standardizes commit messages for automated release notes generation.
Yes, you can include a structured body explaining how or why changes were made, alongside optional trailers like Fixes or Co-authored-by. This adds necessary context for complex software development updates and pull requests.
To indicate a breaking change, the conventional commit message uses specific type formatting and structured body guidance. This clearly signals breaking changes for CI workflows and release notes generation.
When writing conventional commit messages, you should avoid committing secrets, including sensitive files, and writing generic or vague subjects. Safety guardrails prevent exposing sensitive data in your Git repository history.
daikichiba9511Convert git diffs into Conventional Commits compliant commit messages.
ccfGenerate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.
arakitakashiStandardize Git operations with Git Flow branching and Conventional Commits.
xloxn69Format git commit messages using the Conventional Commits specification.