# Commit Message

> Writes a conventional commit message from the staged diff, one logical change at a time.

- **Type:** Skill
- **Install:** `agentstack add skill-bh-rat-steer-commit-message`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [bh-rat](https://agentstack.voostack.com/s/bh-rat)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [bh-rat](https://github.com/bh-rat)
- **Source:** https://github.com/bh-rat/steer/tree/main/examples/commit-message
- **Website:** https://steer-docs.vercel.app/

## Install

```sh
agentstack add skill-bh-rat-steer-commit-message
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## 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

1. Run: `git diff --cached --stat` then `git diff --cached`. If nothing is
   staged, say so and stop; never guess from unstaged changes.
2. 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.
3. Pick the type and scope. When unsure which type fits, first read
   `references/conventional-commits.md`.
4. Write the message: imperative subject ≤ 50 chars
   (`type(scope): change`), blank line, body wrapped at 72 explaining what
   changed and why, not how.
5. 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](https://github.com/bh-rat)
- **Source:** [bh-rat/steer](https://github.com/bh-rat/steer)
- **License:** MIT
- **Homepage:** https://steer-docs.vercel.app/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-bh-rat-steer-commit-message
- Seller: https://agentstack.voostack.com/s/bh-rat
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.