Commit Message

---
name: Commit Message
description: Write a precise Conventional Commits message from the staged diff.
platforms: [universal]
tags: [git, commit, workflow]
version: 1.0.0
author: Motion Mavericks
license: MIT
---

# Commit Message

Generate a commit message that describes **what changed and why**, following the
[Conventional Commits](https://www.conventionalcommits.org) format.

## Instructions

1. Read the staged changes: `git diff --cached`. If nothing is staged, read
   `git diff` and note that the change is unstaged.
2. Determine the primary type: `feat`, `fix`, `refactor`, `docs`, `test`,
   `chore`, `perf`, `build`, or `ci`.
3. Write the subject line: `<type>(<scope>): <summary>`
   - Imperative mood ("add", not "added").
   - No trailing period. Aim for ≤ 50 characters.
   - `scope` is optional; use the affected module/area when it clarifies.
4. If the change is non-trivial, add a body separated by a blank line that
   explains the motivation and any consequences a reviewer should know.
5. Never invent changes. Describe only what the diff actually shows.

## Output

Print only the commit message, ready to pass to `git commit -F -`.