Commit Message
Writes a conventional commit message from the staged diff, one logical change at a time.
Install
$ agentstack add skill-bh-rat-steer-commit-message ✓ 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bh-rat-steer-commit-message) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
commit-message
Turn whatever is currently staged into one well-formed conventional commit message the user can apply as-is. The user gets the message text; you never run git commit yourself.
Steps
- Run:
git diff --cached --statthengit diff --cached. If nothing is
staged, say so and stop; never guess from unstaged changes.
- Check the diff is atomic (one logical change). If it mixes concerns,
propose how to split it (git reset -p / staging hunks) instead of writing a muddled message.
- Pick the type and scope. When unsure which type fits, first read
references/conventional-commits.md.
- Write the message: imperative subject ≤ 50 chars
(type(scope): change), blank line, body wrapped at 72 explaining what changed and why, not how.
- Present the message in a fenced block, then ask whether to adjust tone
or detail.
References
Keep this file lean; put branch-only detail behind pointers so it loads only when that branch is hit:
- When choosing the commit type or handling a breaking change, first read
references/conventional-commits.md.
Gotchas
- Empty staged diff → stop at step 1; do not invent a message.
- Generated/lockfile-only diffs (
uv.lock,package-lock.json) → say the
change is mechanical and suggest chore(deps).
- Never include ticket numbers or co-author trailers unless the user asks.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bh-rat
- Source: bh-rat/steer
- License: MIT
- Homepage: https://steer-docs.vercel.app/
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.