Commit message
Curated catalog of portable Agent Skills for Claude Code, OpenAI Codex, and opencode — an opinionated product→build pipeline (brainstorming, discovery, PRD, research, planning, review) plus skill authoring, security scanning, and infra helpers. Author once, install into any project.
npx -y skills add gabriel-f-santos/coding-agents --skill commit-messageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 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.
What its author says it does
Copied from the file, not written here
Generate a Conventional Commits message from staged changes. Use when the user asks to "write a commit message", "commit message", "gera a mensagem de commit", "commita isso", or right after staging with git add. Reads the staged diff, classifies it (feat/fix/docs/refactor/test/chore/...), and writes a <72-char imperative subject plus an optional body — it presents the message, it does not run the commit. Do not use for PR descriptions or changelogs — those are separate concerns.
SKILL.md
3.1 KB, as published. Nobody here has run it
commit-message — Conventional Commits from staged changes
Turn the staged diff into a clean Conventional Commits message. The skill reads and drafts — it never commits. The user reviews and commits themselves.
Process
- Read the staged changes. Run
git diff --staged --statfor the shape andgit diff --stagedfor the content. If nothing is staged, rungit statusand tell the user togit addfirst — don't invent a diff. - Match the repo's style. Run
git log -5 --pretty=%sand follow the existing convention (scope usage, language, capitalization) when it doesn't conflict with the rules below. - Classify the change against the type table. One commit = one logical change; if the diff mixes unrelated changes, say so and suggest splitting.
- Draft subject + optional body using the output template.
- Self-check against the checklist, fix violations, then present the message in a fenced block for the user to copy. Do not execute the commit.
Conventional Commits types
| Type | Use for |
|---|---|
feat | a new user-facing feature |
fix | a bug fix |
docs | documentation only |
refactor | behavior-preserving code change |
perf | performance improvement |
test | adding/adjusting tests |
build | build system or dependencies |
ci | CI configuration |
chore | maintenance, no src/test change |
style | formatting only (whitespace, semicolons) |
Add a scope in parentheses when it sharpens meaning: feat(auth): …. Append ! (or a
BREAKING CHANGE: footer) for breaking changes: feat(api)!: ….
Output template
<type>(<scope>): <imperative subject, ≤72 chars, no trailing period>
<optional body: what & why, wrapped at ~72 cols. Blank line above.>
<optional footer: BREAKING CHANGE: … / Refs: #123>
Example Input (staged): added JWT verification middleware + a test Output:
feat(auth): verify JWT on protected routes
Add middleware that validates the bearer token and rejects expired or
malformed tokens with 401 before the handler runs.
Self-check (run before presenting)
- Subject ≤ 72 characters
- Imperative mood ("add", not "added"/"adds")
- No trailing period on the subject
- Type is from the table and matches the actual change
- Subject describes the change, not the file ("add retry to fetch", not "edit fetch.ts")
- Body present when the why isn't obvious from the subject; omitted when trivial
- One logical change — flagged the user if the diff mixes concerns