commit

name	commit
description	Stage changes and create a commit with a well-formatted message
argument-hint	[optional message hint]

Commit

Create a git commit for the current changes following project conventions.

Steps

1. Run git status to see all changed and untracked files
2. Run git diff --stat to understand the scope of changes
3. Run git log --oneline -5 to see recent commit message style
4. Stage the relevant files (use specific file names, not git add -A)
5. Write a commit message following the format below
6. Commit and verify success

Commit Message Format

type: short description

- bullet point details
- more details

Types: feat, fix, refactor, docs, test, chore

Rules:

• Do NOT include Co-Authored-By lines
• First line: type + short description (imperative mood, lowercase)
• Bullet points: what changed and why
• Keep it concise — focus on the "what" not the "how"
• Use a HEREDOC to pass the message to git commit -m

If the user provides a hint via $ARGUMENTS, use that to guide the commit message.

If pre-commit hooks modify files

Re-stage the modified files and commit again. Do NOT use --no-verify.