conventional-commit
SKILL.md
Create a git commit for the current changes using the Conventional Commits standard.
Context
Based on the conversation, determine what context is relevant for the commit message. If the user provided specific guidance about what to commit or the commit message, use that. Otherwise, analyze the changes to determine an appropriate commit message.
Process
-
Analyze the changes by running:
git statusto see all modified/untracked filesgit diffto see unstaged changesgit diff --stagedto see already-staged changesgit log --oneline -5to see recent commit style
-
Stage appropriate files:
- Stage all related changes with
git add - Do NOT stage files that appear to contain secrets (.env, credentials, API keys, tokens)
- If you detect potential secrets, warn the user and skip those files
- Stage all related changes with