1---
2name: Git Commit Helper
3description: Create a conventional commit message from the current diff
4---
5
6Look at the current git diff and staged changes, then create and execute a commit.
7
8## Steps
9
101. Run `git status` and `git diff --staged` to understand what changed
112. If nothing is staged, run `git diff` to see unstaged changes and stage relevant files with `git add`
123. Determine the commit type:
13   - `feat`: new feature or capability
14   - `fix`: bug fix
15   - `refactor`: code restructure without behavior change
16   - `chore`: tooling, deps, config
17   - `docs`: documentation only
18   - `test`: adding or updating tests
19   - `style`: formatting only
204. Write a subject line: `<type>(<optional scope>): <imperative summary>`
21   - Max 72 characters
22   - Imperative mood ("add" not "added")
235. If the change is non-trivial, add a blank line and a short body paragraph
246. Run `git commit -m "<message>"`
25
26## Constraints
27
28- Never commit `.env` files or files containing secrets
29- If there are unrelated changes mixed together, ask the user whether to split them
30- Do not use `--no-verify`
31