Enforcement
This skill MUST be followed exactly. Steps MUST execute in order. Do not skip, merge, or reorder any step.
Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types
feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
Rules
- type: Required, lowercase, from the list above
- scope: Optional. Only include when it clearly adds context (e.g.
feat(ui): vs feat:). Lowercase, kebab-case if multi-word.
- description: Required, lowercase start, no period at end, imperative mood (what the change does, not what it did), max 72 chars
- body: Optional, wrap at 100 chars, explain "what" and "why" (not "how")
- footer: Optional, for breaking changes (
BREAKING CHANGE:) or issue refs (Closes #123, Fixes #456)
Breaking Changes
Append ! to type/scope, or add BREAKING CHANGE: footer.
Examples
feat(auth): add OAuth2 login support
fix(ui): resolve button alignment on mobile
docs: update API documentation
refactor(auth): simplify error handling logic
chore(deps): upgrade React to v19
Workflow — Execute in Exact Order
MANDATORY — Run exactly git add -A. Before confirmation, no other git command is allowed, including git config, git status, git diff, or git log.
MANDATORY — Abort if the commit would use an AI author name/email, AI credentials, Co-Authored-By, or --author with an AI identity.
MANDATORY — Generate the commit message in Conventional Commits format.
MANDATORY — Output the commit message on its own line at the END of your response. Nothing — no explanation, no commentary, no emoji — should follow it:
feat(auth): add OAuth2 login
MANDATORY — Wait for user confirmation. If confirmed, run only the direct git commit command for the generated message. If declined, stop.
1---2name: commit3description: Mandatory workflow for any task that generates a git commit or commit message. Use this skill whenever the user asks to commit changes, stage and commit, create a commit, or write a Conventional Commits/commitlint message, even if they do not explicitly say "skill".4---56## Enforcement78**This skill MUST be followed exactly. Steps MUST execute in order. Do not skip, merge, or reorder any step.**910## Format1112```13<type>(<scope>): <description>14[optional body]15[optional footer(s)]16```1718## Types1920`feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`2122## Rules2324- **type**: Required, lowercase, from the list above25- **scope**: Optional. Only include when it clearly adds context (e.g. `feat(ui):` vs `feat:`). Lowercase, kebab-case if multi-word.26- **description**: Required, lowercase start, no period at end, imperative mood (what the change does, not what it did), max 72 chars27- **body**: Optional, wrap at 100 chars, explain "what" and "why" (not "how")28- **footer**: Optional, for breaking changes (`BREAKING CHANGE:`) or issue refs (`Closes #123`, `Fixes #456`)2930## Breaking Changes3132Append `!` to type/scope, or add `BREAKING CHANGE:` footer.3334## Examples3536```37feat(auth): add OAuth2 login support38fix(ui): resolve button alignment on mobile39docs: update API documentation40refactor(auth): simplify error handling logic41chore(deps): upgrade React to v1942```4344## Workflow — Execute in Exact Order45461. **MANDATORY** — Run exactly `git add -A`. Before confirmation, no other `git` command is allowed, including `git config`, `git status`, `git diff`, or `git log`.472. **MANDATORY** — Abort if the commit would use an AI author name/email, AI credentials, `Co-Authored-By`, or `--author` with an AI identity.483. **MANDATORY** — Generate the commit message in Conventional Commits format.494. **MANDATORY** — Output the commit message **on its own line at the END of your response**. Nothing — no explanation, no commentary, no emoji — should follow it:5051 feat(auth): add OAuth2 login52535. **MANDATORY** — Wait for user confirmation. If confirmed, run only the direct `git commit` command for the generated message. If declined, stop.
vainjs