commit-message

SKILL.md

---
name: commit-message
description: Use when writing a commit message. Conventional Commits format with a clean scope and a why-not-what body.
---

# Commit message

Format:

```
<type>(<scope>): <imperative one-liner>

<why this change matters, in 1-2 short paragraphs>
<optional: BREAKING CHANGE section>
```

Rules:
1. `type` ∈ feat | fix | refactor | chore | docs | style | perf | test | security.
2. Subject line under 72 chars, imperative mood ("add", not "added"), no trailing period.
3. Body explains WHY, not WHAT — the diff already shows the what.
4. Reference the ticket / PR (`Closes #123`) at the end of the body when applicable.

Tagi