Conventional Commits

What it does

This skill enables AI agents to generate commit messages that strictly follow the Conventional Commits specification. It ensures every message includes a type (e.g., feat, fix), an optional scope, and a descriptive body, automatically formatting them for tools like changelogs or versioning systems.

When to use it

• Generating standardized commit messages during code review workflows.
• Creating automated changelog entries from git history.
• Enforcing strict message formats in CI/CD pipelines before merging.
• Preparing release notes by parsing structured commit types.

Key capabilities

• Validates and structures commit messages with required prefixes.
• Supports standard types like feat, fix, docs, style, refactor, test, and chore.
• Allows optional scope specification to narrow down affected modules.
• Formats output compatible with semantic versioning tools.

Example prompts

• "Generate a conventional commit message for adding user authentication to the login module."
• "Format this list of changes into valid Conventional Commits: fixed typo in README, added new API endpoint, updated dependencies."
• "Create a changelog entry based on commits that include the 'feat' type from the last release."

Tips & gotchas

Ensure your AI agent has access to the project's specific scope names (e.g., auth, ui) to generate accurate messages. This skill does not automatically detect code changes; it requires clear input describing the modification intent.