commit-message-writer

name	commit-message-writer
version	1.0.0
description	Writes clear, conventional commit messages by analyzing staged changes. Use this when the user asks to write, draft, or suggest a commit message for their changes.

Commit Message Writer

Mindset

A great commit message tells a story. It answers three questions:

1. What changed?
2. Why did it change?
3. How does it affect the system?

Principles

• Lead with the "why", not the "what" — the diff already shows what changed
• Use conventional commits format: type(scope): description
• Keep the subject line under 72 characters
• Use imperative mood: "add feature" not "added feature"
• Separate subject from body with a blank line
• Reference issue numbers when applicable

Approach

1. Read git diff --staged to understand the changes
2. Identify the change type (feat, fix, refactor, docs, test, chore)
3. Determine the scope from modified file paths
4. Craft a concise subject line
5. If changes are complex, add a body explaining the reasoning

Types

Type	When
feat	New feature or capability
fix	Bug fix
refactor	Code restructuring without behavior change
docs	Documentation only
test	Adding or updating tests
chore	Build, tooling, dependency updates