| name | commit |
| description | Create a git commit with proper context and conventional commit message |
| disable-model-invocation | true |
Create a git commit for the current changes.
- Run
git status and git diff --staged (and git diff if nothing staged) to understand the changes
- Run
git log --oneline -5 to see recent commit message style
- Draft a concise commit message:
- Use conventional commit format:
feat:, fix:, refactor:, docs:, test:
- Focus on WHY, not WHAT (the diff shows what)
- One sentence, under 72 characters for the subject line
- Stage relevant files (prefer specific files over
git add -A)
- Never commit
.env, credentials, or large binaries
- Show the commit message and ask for confirmation before committing