Git Commit
Write a clear, conventional commit message from the staged diff.
Install
$ agentstack add skill-brattlof-skillet-git-commit ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Brattlof
- Source: Brattlof/skillet
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.