Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Added metadata section with author and version information to the skill definition. - No changes to functionality or documentation content.
What This Skill Does
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.
When to use it
- 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
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: write a commit message for adding OAuth2 login support
- 1Identifies the change as a new feature
- 2Selects the feat type with an appropriate scope (auth)
- 3Writes the description in imperative mood, lowercase, no trailing period
- 4Checks whether any breaking changes require the ! flag or BREAKING CHANGE footer
feat(auth): add OAuth2 login support