From ai-dev-extensions
Use when creating git commits - enforces Conventional Commits specification for semantic versioning compatibility
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-dev-extensions:git-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
All git commit messages MUST follow the [Conventional Commits](https://www.conventionalcommits.org/) specification. This enables automatic semantic versioning, changelog generation, and clear project history.
All git commit messages MUST follow the Conventional Commits specification. This enables automatic semantic versioning, changelog generation, and clear project history.
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
| Type | Description | SemVer Impact |
|---|---|---|
feat | New feature | MINOR |
fix | Bug fix | PATCH |
docs | Documentation only | - |
style | Formatting, missing semicolons, etc. (no code change) | - |
refactor | Code change that neither fixes a bug nor adds a feature | - |
perf | Performance improvement | PATCH |
test | Adding or correcting tests | - |
build | Changes to build system or external dependencies | - |
ci | Changes to CI configuration files and scripts | - |
chore | Other changes that don't modify src or test files | - |
revert | Reverts a previous commit | - |
A breaking change MUST be indicated by:
! after the type/scope: feat!: remove deprecated APIBREAKING CHANGE: footer in the commit bodyBreaking changes trigger a MAJOR version bump.
Before committing, check the current branch:
git branch --show-current
If you are on the default branch (main or master), you MUST create and switch to a new branch before committing. The branch name MUST follow the convention:
<type>/<short-description>
Where <type> matches the Conventional Commits type of the work being done.
# BAD - committing on main
git commit -m "feat: add login page"
# GOOD - create branch first, then commit
git checkout -b feat/add-login-page
git commit -m "feat: add login page"
feat, fix, perf, docs, refactor, ci, test, build, chore)# Examples
feat/oauth2-login-flow
fix/null-response-payment
perf/optimize-query-cache
docs/add-installation-guide
refactor/extract-auth-middleware
ci/pin-actions-to-sha
Use this command to determine the default branch:
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@refs/remotes/origin/@@' || echo "main"
# BAD
git commit -m "add login page"
# GOOD
git commit -m "feat: add login page"
Scope should be a noun describing the section of the codebase:
# GOOD
git commit -m "feat(auth): add OAuth2 login flow"
git commit -m "fix(api): handle null response from payment gateway"
git commit -m "ci(github-actions): upgrade checkout action to v4"
# BAD
git commit -m "feat: Added login page."
git commit -m "feat: Adds login page"
# GOOD
git commit -m "feat: add login page"
# With ! marker
git commit -m "feat(api)!: change authentication endpoint response format"
# With footer
git commit -m "feat(api): change authentication endpoint response format
BREAKING CHANGE: response now returns a JWT token instead of session ID"
# GOOD
git commit -m "fix(parser): handle edge case with empty arrays
The parser crashed when receiving an empty array from the API.
Root cause was a missing null check in the deserialization step."
# Feature
feat(dashboard): add real-time metrics widget
# Bug fix
fix(auth): prevent token refresh race condition
# Documentation
docs(readme): add installation instructions for OpenCode
# CI
ci(workflows): pin actions to SHA for supply chain security
# Breaking change
feat(api)!: migrate from REST to GraphQL endpoints
BREAKING CHANGE: all /api/v1/* endpoints are removed, use /graphql instead
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 using-system/ai-dev-extensions --plugin ai-dev-extensions