| name | commit-format |
| description | Formats GitHub commit messages following Conventional Commits style with title and optional description. Use when proposing or implementing code changes, writing commit messages, or when the user asks for commit message suggestions. |
Commit Format
Template (copy this structure exactly)
Title only — raw markdown:
> **Commit title:** `type(scope): short description here`
Title with description — raw markdown:
> **Commit title:** `type(scope): short description here`
>
> Description sentence one. Description sentence two with `codeRef()` references.
Rules
- Use markdown blockquote (
> prefix) — no exceptions
- Title goes after
**Commit title:** wrapped in exactly ONE backtick pair
- NEVER put backticks inside the title — the whole title is one code span, no nesting
- Description uses backticks for code references — title does NOT
- Conventional Commits types:
fix, feat, perf, refactor, docs, chore
- Always include a scope — a short, human-readable area name (e.g.
reply modal, mod queue), matching how this repo actually commits (see the commit skill)
- Use
perf for performance optimizations (not fix)
- Description: 2-3 sentences about the solution, no bullet points, only if title isn't enough
Wrong vs Right
❌ WRONG — missing backticks around title:
> **Commit title:** refactor(mod queue): rename from /queue to /modqueue
❌ WRONG — backticks around individual words instead of whole title:
> **Commit title:** refactor(mod queue): rename from `/queue` to `/modqueue`
❌ WRONG — missing scope:
> **Commit title:** `refactor: rename from /queue to /modqueue`
✅ CORRECT — entire title in one backtick pair, no backticks inside, scope present:
> **Commit title:** `refactor(mod queue): rename from /queue to /modqueue`
Self-check
Before outputting, verify:
