// Create well-formatted git commits. Use when the user wants to commit changes, stage files, write a commit message, or run a git commit workflow. Triggers on requests like "commit my changes", "make a commit", "/commit".
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | commit |
| description | Create well-formatted git commits. Use when the user wants to commit changes, stage files, write a commit message, or run a git commit workflow. Triggers on requests like "commit my changes", "make a commit", "/commit". |
Create clean, descriptive git commits following best practices.
Run in parallel:
git status # see untracked/modified files
git diff --staged # see already-staged changes
git diff # see unstaged changes
git log --oneline -5 # understand commit message style used in this repo
Read relevant changed files if needed to understand what was modified and why.
Stage only relevant files — never blindly git add .:
git add <specific-files>
Warn the user and skip files that look sensitive (.env, *.key, credentials.*, secrets.*).
Follow the repo's existing style. If no clear style, use Conventional Commits:
<type>(<scope>): <short summary>
<optional body explaining the why>
Types: feat, fix, refactor, docs, test, chore, style, perf
Rules:
Fixes #123git commit -m "$(cat <<'EOF'
<type>(<scope>): <summary>
<body if needed>
EOF
)"
Show the commit hash and summary. Ask if the user wants to push.
<hash> <message><current-branch>?"