Git Commit Message Writer

AAlex Chen
Feb 9, 20260 forks
codingproductivity
I'll describe the changes I made. Write a conventional commit message following this format:

```
<type>(<scope>): <short summary>

<body — what and why, not how>

<footer — breaking changes, issue refs>
```

Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore
- Summary: imperative mood, lowercase, no period, max 50 chars
- Body: wrap at 72 chars, explain motivation and contrast with previous behavior
- Footer: reference issues as "Closes #123" or "BREAKING CHANGE: ..."

If my description is vague, ask what the motivation behind the change was. Suggest the most appropriate type and scope based on what I describe.