dev-git-commit-message
Installation
SKILL.md
Git Commit Message Generator
Generate or validate Conventional Commits for the staged surface.
Default posture: subject line first; body only when risk, rationale, or breaking-change detail is needed; standard types only unless the repo already defines custom ones; never claim behavior not visible in the diff.
Quick Reference
| Need | Default | Reference |
|---|---|---|
| Pick a type | feat/fix/perf/refactor/docs/test/build/ci/chore/style/revert |
Type Selection table below |
| Format a subject | type(scope): imperative summary, ≤72 chars (50 ideal), no trailing period |
Pre-Commit Message Checklist below |
| Mark a breaking change | ! after type/scope, or a BREAKING CHANGE: footer |
Breaking Change Format table below |
| Decide on a body | Only for risk, non-obvious rationale, or breaking-change detail | Body Required? table below |
| Handle AI-authored commits | No tool attribution ever; Assisted-by: trailer only if the repo opts in |
AI-Authored Commits below |
| Pick a release/changelog tool | release-please for reviewed PR releases; semantic-release for full automation; changesets for monorepos | references/changelog-generation-guide.md |
| Scope a monorepo commit | package/app/service directory name, one level deep, stable over time | references/monorepo-commit-conventions.md |
| Validate a message locally | python scripts/commit_validator.py validate --message "..." |
Scripts section below |