commit
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.
sneg55 · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add sneg55/agent-starter --skill commitAbout this skill
name: commit description: Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message. user_invocable: true allowed-tools:
- Bash(git add:*)
- Bash(git status:*)
- Bash(git commit:*)
Git Commit
Context
Gather this context before committing:
- Current git status:
git status - Current git diff (staged and unstaged):
git diff HEAD - Current branch:
git branch --show-current - Recent commits:
git log --oneline -10
Git Safety Protocol
- NEVER update the git config
- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
- CRITICAL: ALWAYS create NEW commits. NEVER use git commit --amend, unless the user explicitly requests it
- Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files
- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
- Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported
Task
Based on the changes, create a single git commit:
-
Analyze all staged changes and draft a commit message:
- Look at the recent commits to follow this repository's commit message style
- Summarize the nature of the changes (new feature, enhancement, bug fix, refactoring, test, docs, etc.)
- Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.)
- Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
-
Stage relevant files and create the commit using HEREDOC syntax:
git commit -m "$(cat <<'EOF'
Commit message here.
EOF
)"
Stage and create the commit in a single message. Do not do anything else.