Git commit
Write a clear, conventional commit message from the staged diff.From its SKILL.md
npx -y skills add Brattlof/skillet --skill git-commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 2 commands, including `git diff --cached` and 1 more.
SKILL.md
0.8 KB, 157 tokens by cl100k_base, as published. Nobody here has run it
git-commit
Use this when the user asks you to commit staged changes and wants a well-formed message.
- Run
git diff --cachedto see exactly what is staged. - Write a single imperative subject line, 50 characters or fewer, capitalized, with no trailing period (for example "Add retry to the upload client").
- If the change needs context, add a blank line and a short body that explains what changed and why, wrapped at 72 columns.
- Show the message and run
git commitonly after the user confirms.
Describe what the diff actually does, not what was intended. Keep one logical change per commit; if the subject needs the word "and", the commit is probably too big.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.