Commit message writer

Skill kakarot-oncloud/claude-dev-skills/skills/commit-message-writer

Writes clean Conventional Commits messages from a git diff, staged changes, or a plain-English description of what changed. Use this skill whenever the user asks for a commit message, says "what should I write for this commit", pastes a diff and wants it summarized, or asks to follow conventional commits / semantic commit format.From its SKILL.md

Install

npx -y skills add kakarot-oncloud/claude-dev-skills --skill commit-message-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 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.

SKILL.md

2.0 KB, 432 tokens by cl100k_base, as published. Nobody here has run it

Commit Message Writer

You write commit messages that follow the Conventional Commits 1.0.0 specification.

Format

<type>(<optional scope>): <subject>

<optional body>

<optional footer>

Allowed types

feat — new feature
fix — bug fix
docs — documentation only
style — formatting, no code change
refactor — code change that is not a feature or fix
perf — performance improvement
test — adding or fixing tests
build — build system or dependencies
ci — CI configuration
chore — other maintenance
revert — reverts a previous commit

Rules

Subject line ≤ 72 chars, imperative mood ("add" not "added"), no trailing period, lowercase after the colon.
Body wraps at 72 chars, explains what and why, not how.
Breaking changes → add ! after type/scope AND a BREAKING CHANGE: footer.
Issue refs in footer: Closes #123, Refs #456.
If the diff touches multiple unrelated areas, suggest splitting the commit and offer one message per logical change.

Process

Read the diff or description carefully.
Identify the single primary change.
Pick the correct type (default to chore only if nothing else fits).
Write subject, then body only if the change isn't self-explanatory.
Output the message in a fenced code block, ready to paste into git commit -m.

Example output

feat(auth): add refresh token rotation

Tokens now rotate on every refresh and old tokens are blacklisted
for 5 minutes to handle in-flight requests gracefully.

Closes #284

Never invent changes that aren't in the diff. If the diff is unclear, ask one focused question before writing.

What ships with it: 1 file

1.2 KB alongside SKILL.md

README.md1.2 KB