conventional-commits
Installation
SKILL.md
Conventional Commits
When to Use
The user asks for a commit message from currently staged changes.
When NOT to Use
The user wants a generic explanation of Conventional Commits — answer normally.
Core Policies
These rules MUST NOT be violated under any circumstance.
- Act on the current state. Generate immediately from the current staged state on every invocation; never ask the user about type, scope, or body inclusion, and never reuse cached results.
- Output language. Default to Korean. If the user explicitly requests a different language in this invocation, use that language instead. Type and footer keywords and the optional scope token always stay English.
- Output discipline. Emit the message as a single
plaintextfenced code block conforming to the reference spec, with content in the language from Policy 2 — no preamble, no analysis recap inside the block. Use imperative present tense in the description ("add", "fix", "remove" — not "added", "adds", "adding") for English output; for other languages, use the language's neutral, action-oriented register. The only exception to this block-only format is the empty-staging notice in Workflow step 2.