Stats
Actions
Tags
From commit-commands
Git workflow conventions for committing, branching, and PRs. Covers commit message style, branch naming, and PR structure. Consult when creating commits or pull requests in any project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/commit-commands:git-conventionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Follow conventional commits format when appropriate:
Follow conventional commits format when appropriate:
<type>: <short summary>
<optional body>
| Type | Usage |
|---|---|
feat | A new feature |
fix | A bug fix |
refactor | A code change that neither fixes nor adds |
chore | Maintenance, config, deps |
docs | Documentation only |
style | Formatting, missing semicolons, etc. |
test | Adding or correcting tests |
Use descriptive branch names with a type prefix:
<type>/<short-description>
Examples: feat/add-user-auth, fix/login-error, refactor/api-client.
Include in every PR description:
Never stage or commit files that contain secrets:
.env filescredentials.json*.pem private keysAlways check .gitignore before staging files.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub pau-vega/devkit-ai --plugin commit-commands