
Conventional Commit
This walks you through the Conventional Commits spec with practical examples and a prerequisite check to keep you off the main branch. You get a clean table of commit types (feat, fix, refactor, etc.), formatting rules like the 70-character subject line limit, and real examples showing how to handle breaking changes and reverts. The guidance on writing bodies is solid: explain what and why, not how. If you've been on teams where commit messages are a mess or you're trying to enable semantic versioning, this gives you a consistent template. It's opinionated in the right ways, like insisting on imperative mood and branch naming that matches commit types.
- skills.sh installs
- 962
- GitHub stars
- 19
- last updated
- Aug 21, 2026
Install
$ npx -y skills add marcelorodrigo/agent-skills --skill conventional-commit --agent claude-codeInstalls into .claude/skills of the current project.
Files
Conventional Commit Messages
Follow these conventions when creating commits.
Prerequisites
Before committing, ensure you're working on a feature branch, not the main branch.
# Check current branch
git branch --show-current
If you're on main or master, create a new branch first:
# Create and switch to a new branch
git checkout -b <type>/<short-description>
Branch naming should follow the pattern: <type>/<short-description> where type matches the commit type (e.g., feat/add-user-auth, fix/null-pointer-error, refactor/extract-validation).
Format
<type>(<scope>): <subject>
<body>
<footer>
The header is required. Scope is optional. All lines must stay under 100 characters.
Commit Types
Sponsors
Details
- Repository
- github.com/marcelorodrigo/agent-skills
- Categories
- Git & Pull Requests, Documentation, AI & Agent Building
- First seen
- May 16, 2026