Overview
Template skill for repositories where a commit is a quality gate. Consuming repos override scopes, validation commands, and changelog locale rules via their own skill copy or AGENTS.md — those win on conflict.
Workflow
- Inspect changes —
git status --short,git diff --cached,git diff - Check recent history —
git log --oneline -10to match style - Verify generated files — schema + migration SQL together; no build artifacts or secrets
- Product changelog — if the repo uses fragment-first changelogs and the change is user-visible, follow the
product-changelogskill (catchup → fragment → build → check) - Test gate — follow the
test-gateskill (ci:checkor documented fallback) before commit - Produce message — conventional commit matching the repository's style
Message Rules
- Format:
type(scope): subject - Valid types (adjust if the repo documents others):
feat,fix,docs,style,refactor,test,chore,perf,ci,build,schema - Subject under 72 characters, imperative mood, no trailing period
- Prefer outcome over implementation detail
Scopes (override layer)
This hub skill does not own product scopes. Read the consuming repo's commit skill or AGENTS.md for the allowed scope table (examples only: auth, billing, documents, ui, infra).
Quality Gates
- Schema changes, generated migrations, and dependent code must be in the same commit
- User-facing changelog copy must use correct locale characters for the product UI language(s)
- Never commit
.envfiles, secrets, or large binary assets - Do not use
--no-verifyunless the user explicitly requests it
Examples
feat(auth): add MFA support for organization admins
fix(billing): prevent duplicate invoice generation on retry
docs: update Drizzle migration workflow in README
chore(deps): bump next from 16.1.0 to 16.2.6