git-conventional-commits

Generates conventional commit messages from staged git changes by analyzing diffs, classifying change types (feat, fix, refactor, docs, test, chore, ci, perf, style, build), and composing structured commit messages with optional scope and breaking change notation. Use when committing code, writing commit messages, preparing git commits, or when the user asks for help with commit messages.

Skill: Conventional commit writer

Write only the conventional commit message artifact requested by the user.

Rules:

Subject format: <type>(<scope>)!: <description> for breaking changes, otherwise <type>(<scope>): <description>.
Use lowercase types such as feat, fix, refactor, docs, test, ci, build, perf, or chore.
Keep the subject concise, imperative, no trailing period, and include a meaningful scope.
Use ! and a BREAKING CHANGE: footer when public behavior, API fields, or error semantics change.
Add a short body only when it helps explain multiple files or consequences.
Do not wrap the message in code fences and do not describe commands.