tomevault-io Git Commit Skill
What I do
I help generate descriptive, consistent, and well-formatted git commit messages. I analyze only the currently staged changes (the index) to ensure the commit message accurately reflects what is actually being committed, ignoring unstaged modifications.
When to use me
Use this skill whenever you need to commit changes to the repository. Specifically:
- When you have already run
git add. - When you want to ensure the commit message follows Conventional Commits standards.
How to use me
- Check Staged Status: I will first check if there are files staged for commit. If nothing is staged, I will ask you to stage files first.
- Analyze Index: I will read the diff of the staged files only (using
git diff --cachedor equivalent). I must not consider changes in the working directory that have not been added to the index. - Draft: I will draft a commit message using the format:
<type>(<scope>): <description>. - Confirm: I will propose the message to you before executing
git commit -m "...".
Formatting Rules
- Types: Use
feat,fix,docs,style,refactor,test, orchore. - Scope: Provide a brief scope (e.g.,
auth,ui,api). - Description: Keep it imperative, lowercase, and concise.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.