conventional-commits
от bastos
Git & GitHubКратко
Format commit messages using the Conventional.
Описание
Что делает этот навык
Formats commit messages according to the Conventional Commits specification, which maps commit types like feat and fix to semantic version increments. Structured messages enable automated changelog generation and release tooling.
Structured commit types let release tools like semantic-release determine version bumps automatically without manual tagging or release notes.
Когда его использовать
- Writing a commit message for a new feature
- Marking a breaking API change with the correct notation
- Scoping a bug fix to a specific module
- Preparing commits that feed into automated changelog tools
- Standardizing commit history across a team
Пример сценария
User asks: write a commit message for adding OAuth2 login support
- 1
Identifies the change as a new feature
- 2
Selects the feat type with an appropriate scope (auth)
- 3
Writes the description in imperative mood, lowercase, no trailing period
- 4
Checks whether any breaking changes require the ! flag or BREAKING CHANGE footer
feat(auth): add OAuth2 login support
Установка
clawhub install bastos/conventional-commitsВыполните команду CLI или вставьте промпт в Claude Code, Cursor, Codex — любой кодинг-агент, которым пользуетесь.