Commit message
A collection of Agent Skills — self-contained folders that teach AI agents to perform specialized tasks. Includes a production-readiness harness-audit skill, a plugin marketplace, a SKILL.md spec, and CI validation.
npx -y skills add contextosai/skills --skill commit-messageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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
Write a clear, conventional git commit message from staged changes. Use when the user asks to commit, write a commit message, or describe what changed.
SKILL.md
1.4 KB, as published. Nobody here has run it
Commit Message
Generate a high-quality commit message that describes the staged changes.
Steps
- Run
git diff --stagedto see what is actually being committed. If nothing is staged, inspectgit statusand ask the user what to stage. - Identify the single primary intent of the change. If the diff does more than one unrelated thing, suggest splitting it into multiple commits.
- Write the message using the Conventional Commits format.
Format
<type>(<optional scope>): <subject>
<body — what changed and why, wrapped at ~72 cols>
- type: one of
feat,fix,refactor,docs,test,chore,perf,build,ci. - subject: imperative mood, lowercase, no trailing period, ≤ 50 chars.
- body: optional. Explain why, not just what. Omit for trivial changes.
Guidelines
- Describe the effect of the change, not the mechanics of editing files.
- Never invent a rationale that isn't supported by the diff.
- One logical change per commit.
Examples
feat(auth): add refresh-token rotation
Tokens are now rotated on every refresh so a leaked token is valid for
at most one cycle.
fix(parser): handle empty input without panicking