commit-message-writerlisted

# Commit Message Writer ## When to use this - The user shares a `git diff` or `git status` output and asks for a commit message. - The user describes what they changed in plain language and wants it turned into a commit message. - The user asks to "clean up" or "improve" an existing commit message. ## Steps 1. **Identify the type of change** from the diff or description. Use one of: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `style`, `perf`, `build`, `ci` 2. **Identify the scope** (optional but preferred when clear) — the module, file, or feature area affected. Keep it short (one word or hyphenated phrase). 3. **Write the subject line**: - Format: `type(scope): short imperative summary` - Imperative mood ("add", "fix", "remove" — not "added", "fixes", "removing") - No period at the end - Under 72 characters - Lowercase after the colon, unless a proper noun 4. **Write the body** (only if the change needs explaining beyond the subject): - Explain *why*, not just *what* — the diff already shows what changed - Wrap at ~72 characters per line - Separate from the subject with one blank line 5. **Add a footer** only if relevant: - `BREAKING CHANGE: <description>` for breaking changes - `Fixes #123` / `Closes #123` for issue references 6. If the diff contains multiple unrelated changes, say so explicitly and suggest splitting into multiple commits rather than writing one message that tries to cover everything. ## Example **Input (di