skills.rest
bramanda48
bramanda48COMMUNITY
Explore all skills by this author →
WebsiteGitHub

conventional-commits

Formats git commit messages according to the Conventional Commits specification.

Updated Sep 17, 2026
Search Tags:#git#changelog#version control#conventional commits#commit messages#semantic versioning
One-click install
npx skills add https://github.com/bramanda48/skills --skill conventional-commits-bramanda48
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/bramanda48/skills/tree/main/skills/conventional-commits
Command: npx skills add https://github.com/bramanda48/skills --skill conventional-commits-bramanda48

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent commit messages break automated changelog generation, semantic versioning, and release tooling. This Skill ensures every commit message follows the Conventional Commits specification so your git history stays machine-readable and release automation works correctly. ## Core Features & Use Cases - Standardized Commit Format: Enforces the type/scope/description structure with types like feat, fix, docs, refactor, perf, test, build, ci, chore, and revert. - Breaking Change Notation: Supports both the ! marker and BREAKING CHANGE footer for signaling major version bumps. - Semantic Versioning Mapping: Maps commit types to version bumps (fix to PATCH, feat to MINOR, breaking changes to MAJOR). - Use Case: When you ask the AI to commit your staged changes, it produces a properly formatted message like feat(auth): add OAuth2 support instead of a vague or incorrectly styled message. ## Quick Start Ask the AI to commit your staged changes using a conventional commit message, for example: commit my changes with a conventional commit message.

Frequently Asked Questions about conventional-commits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conventional commit message?▼

Start with a type like feat or fix, optionally add a scope in parentheses, then a colon and a short imperative description. For example: feat(auth): add OAuth2 support. Keep the description lowercase, under 72 characters, and without a trailing period.

What commit types does Conventional Commits support?▼

The required types are feat for new features and fix for bug fixes. Common additional types include docs, style, refactor, perf, test, build, ci, chore, and revert, each describing a different category of change.

How do I mark a breaking change in a commit message?▼

Add an exclamation mark after the type or scope, like feat!: or feat(api)!:, or include a BREAKING CHANGE footer in the commit body. Both methods signal a MAJOR version bump under semantic versioning, and they can be combined.

How do conventional commits map to semantic versioning?▼

A fix commit triggers a PATCH bump (1.0.0 to 1.0.1), a feat commit triggers a MINOR bump (1.0.0 to 1.1.0), and any commit with a breaking change triggers a MAJOR bump (1.0.0 to 2.0.0).

What are common conventional commit mistakes to avoid?▼

Avoid past tense or capitalized descriptions like 'Added new feature', vague messages like 'fix: bug', redundant phrasing like 'feat: add feature', and trailing periods. Use imperative mood, be specific about what changed, and keep descriptions concise.

Related Skills

Explore More Software Engineering Skills→
nabi-channabi-chan

commit

Organize Git changes into atomic commits with conventional commit messages.

Community
Intermediate
LLLLimboLLLLimbo

changelog-automation

Generate release notes and changelogs from commits, PRs, and releases.

Community
Intermediate
unrealandychanunrealandychan
1

commit-hygiene

Enforce Conventional Commits rules on Git commit messages.

Community
Advanced
simpleapps-comsimpleapps-com

conventional-commits

Enforce Conventional Commits v1.0.0 formatting for Git commit messages.

Official
Basic