Create commit messages following conventional commit conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with issue references.
View on GitHubmpuig/skills
mpuig-skills
plugins/mpuig-skills/skills/commit/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/mpuig/skills/blob/main/plugins/mpuig-skills/skills/commit/SKILL.md -a claude-code --skill commitInstallation paths:
.claude/skills/commit/# Commit Messages Follow these conventions when creating commits for Python projects. ## Prerequisites Before committing, ensure you're working on a feature branch, not the main branch. ```bash # Check current branch git branch --show-current ``` If you're on `main` or `master`, create a new branch first: ```bash # 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`, `ref/extract-validation`). ## Format ``` <type>(<scope>): <subject> <body> <footer> ``` The header is required. Scope is optional. All lines must stay under 100 characters. ## Commit Types | Type | Purpose | |------|---------| | `feat` | New feature | | `fix` | Bug fix | | `ref` | Refactoring (no behavior change) | | `perf` | Performance improvement | | `docs` | Documentation only | | `test` | Test additions or corrections | | `build` | Build system or dependencies | | `ci` | CI configuration | | `chore` | Maintenance tasks | | `style` | Code formatting (no logic change) | | `meta` | Repository metadata | | `license` | License changes | ## Subject Line Rules - Use imperative, present tense: "Add feature" not "Added feature" - Capitalize the first letter - No period at the end - Maximum 70 characters ## Body Guidelines - Explain **what** and **why**, not how - Use imperative mood and present tense - Include motivation for the change - Contrast with previous behavior when relevant ## Footer: Issue References Reference issues in the footer using these patterns: ``` Fixes GH-1234 Fixes #1234 Refs #1234 ``` - `Fixes` closes the issue when merged - `Refs` links without closing ## AI-Generated Changes When changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer: ``` Co-Authored-By: Claude <noreply@anthropic.com> ``` This is th