
Conventional Commits
- 56 installs
- 59 repo stars
- Updated June 5, 2026
- dgalarza/claude-code-workflows
Writes Git commit messages that follow the Conventional Commits v1.0.0 spec - correct type, scope, and structure for a clean, automation-friendly history.
About
Conventional Commits is a Claude skill that guides you to write Git commit messages following the Conventional Commits v1.0.0 specification - the right type, optional scope, description, body and footer. A solo builder reaches for it when committing code or reviewing PR history to keep an explicit, tool-parseable commit log that powers automated changelogs and semantic versioning.
- Enforces Conventional Commits v1.0.0 structure
- Correct type/scope/description formatting
- Feeds automated changelogs and semver
- Consistent history across contributors
Conventional Commits by the numbers
- 56 all-time installs (skills.sh)
- Ranked #285 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dgalarza/claude-code-workflows --skill conventional-commitsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 56 |
|---|---|
| repo stars | ★ 59 |
| Last updated | June 5, 2026 |
| Repository | dgalarza/claude-code-workflows ↗ |
What it does
Writes Git commit messages that follow the Conventional Commits v1.0.0 spec - correct type, scope, and structure for a clean, automation-friendly history.
Who is it for?
Teams wanting consistent, automation-friendly commit history
When should I use this skill?
Creating a git commit or reviewing commit messages in a PR
What you get
- formatted commit message
Related skills
FAQ
What spec does it follow?
Conventional Commits v1.0.0, with types like feat, fix, docs, refactor and optional scopes.
Why use conventional commits?
They make history human- and machine-readable, enabling automated changelogs and semantic-version bumps.