commit-message
Skill0 starsChanged 6 months agoMITView on GitHub
Generates Git commit messages from staged or unstaged diffs using imperative subjects, optional scannable body, issue footers when applicable, and ASCII-only output. Use when the user asks for a commit message, help committing, or summarizing changes for a commit.
75 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- AcademySoftwareFoundation/OpenShadingLanguagetheir own version, first seen Nov 16, 2026
- Eclipter/agentstheir own version, first seen Nov 16, 2026
- travissmithv1/claude-skillstheir own version, first seen Nov 16, 2026
- antick/skillstheir own version, first seen Nov 16, 2026
- beecode-rs/claude-skillstheir own version, first seen Nov 16, 2026
- Citxen/Claude-Skillstheir own version, first seen Nov 16, 2026
Used with
Projects with it also use pr-description, api-docs and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillpr-description
Draft Nacelle PR titles, pull request descriptions, commit titles, commit descriptions, and squash commit messages. Use when asked for PR or commit wording, a branch summary, or a PR description that can be used in a commit. Omit validation sections from commit bodies and remove filler.
Also in 12 projects that use this
LangChainSkillapi-docs
OpenAPI documentation and REST API design patterns
Also in 3 projects that use this
srclightSkillrefactor-safely
This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.
Also in 3 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 4 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 11 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 3 projects that use this
Other versions75 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- mab-go/xmind-mcp★ 946% same
Wrote their own version · 74
- zulip/zulip★ 26ksame name
- mergisi/awesome-openclaw-agents★ 4.1ksame name
- AltraMayor/f3★ 3.4ksame name
- github/copilot-cli-for-beginners★ 2.9ksame name
- AcademySoftwareFoundation/OpenImageIO★ 2.4ksame name
- AcademySoftwareFoundation/OpenShadingLanguage★ 2.3ksame name
- sheshbabu/zen★ 1.2ksame name
- s-kostyaev/ellama★ 963same name
- tektoncd/operator★ 612same name
- danielvm-git/bigpowers★ 292same name
64 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ask-questionsSkill
- make-todosSkill
- review-planSkill
- smoke-testSkill
- verify-changesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 20 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 64 edited versions we read keep these.
20
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read the project's agent instructions (e.g.
- Distinctive: line 17
Before generating a message:
- Very specific: line 19
Check for failures: If the project has a build/test/lint workflow, confirm it passes or the user has acknowledged failures.
- Distinctive: line 20
Determine scope: If both staged and unstaged changes exist, ask the user which set the message should cover.
- Distinctive: line 24
If there are staged changes (git diff --staged): produce the message for the commit the user is about to make.
- Distinctive: line 25
If nothing is staged but there are unstaged changes (git diff): produce a proposed message for those working tree changes.
- Distinctive: line 26
If there are no local changes: ask whether to summarize the most recent commit (git show -1 --stat and git show -1 -p) for reference/amend …
- Distinctive: line 32
If anything needed to infer intent is missing, ask before generating.
- Distinctive: line 36
Use ASCII only in the commit message.
- Very specific: line 37
Never use smart punctuation (e.g.
- Distinctive: line 54
Must pass: prepend "If applied, this commit will " to the subject.
- Distinctive: line 70
Omit: if the diff is truly trivial (e.g.
- Distinctive: line 72
Start with 1-2 sentences explaining motivation or impact (avoid restating the subject).
- Distinctive: line 73
Add labeled sections for scannability when helpful:
- Very specific: line 84
Use - bullets. Sub-bullets: indent 2 spaces.
- Distinctive: line 90
Do not add Co-Authored-By, Signed-off-by, or other trailers unilaterally.
- Distinctive: line 91
Place trailers after a blank line following the body (or subject if no body).
- Distinctive: line 98
If no issue ID is provided, omit the footer entirely.
- Distinctive: line 102
When a diff spans multiple unrelated concerns (e.g.
- Distinctive: line 105
If the user wants one commit: Use the primary change as the subject.
- Distinctive: line 110
Do not generate a message and then immediately run git commit unless the user explicitly asked you to commit.
- Distinctive: line 111
Do not invent issue IDs or claim behavior changes not supported by the diff.
- Distinctive: line 112
Do not add trailers (Co-Authored-By, etc.) unless explicitly requested.
- Very specific: line 154
Run /verify-changes before generating a commit message to ensure the build passes.
“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Commit Message
Read the project's agent instructions (e.g. AGENTS.md) before applying this skill to ensure conventions are followed.
When to apply
- User asks for a commit message, help committing, or summarizing changes
- User invokes
/commit-message
Pre-flight
Before generating a message:
- Check for failures: If the project has a build/test/lint workflow, confirm it passes or the user has acknowledged failures. Do not generate a commit message for code that does not build.
- Determine scope: If both staged and unstaged changes exist, ask the user which set the message should cover. Do not silently choose.
Input (in order of preference)
- If there are staged changes (
git diff --staged): produce the message for the commit the user is about to make. - If nothing is staged but there are unstaged changes (
git diff): produce a proposed message for those working tree changes. - If there are no local changes: ask whether to summarize the most recent commit (
git show -1 --statandgit show -1 -p) for reference/amend use.
Output
- Return the full commit message inside a single Markdown code fence.
- This skill generates the message text only; it does not execute
git commit. If the user explicitly says "commit this" or "make the commit," execute the commit with the generated message. - If anything needed to infer intent is missing, ask before generating.
Character policy
- Use ASCII only in the commit message.
- Never use smart punctuation (e.g. curly quotes, em dashes). Use straight apostrophe (
'), straight quotes ("), and hyphens (-) only. - Self-check for non-ASCII before returning. Replace any with ASCII equivalents.
Required format
<Subject line>
<Body (optional)>
Closes #<ID> (only if an ID is provided)Subject line
- Imperative mood, capitalized, no trailing period.
- Aim for ~50 characters (hard max 72).
- Must pass: prepend "If applied, this commit will " to the subject; the result must read as natural English.
Examples:
Add runtime startup validationFix WebSocket reconnection logicUpdate Ant Design to v6
Counterexamples (do not do this):
Added runtime startup validation(past tense)fix websocket bug(not capitalized)Update Ant Design to v6.(trailing period)
Body (optional; prefer WHY over HOW)
- Omit if the diff is truly trivial (e.g. typo, formatting, comment-only) and there is no meaningful motivation to record.
- Wrap at 72 characters.
- Start with 1-2 sentences explaining motivation or impact (avoid restating the subject). "This commit ..." is encouraged if natural, but not required.
Add labeled sections for scannability when helpful:
Features: - ... Changes: - ... Fixes: - ...- Use
-bullets. Sub-bullets: indent 2 spaces. Wrapped continuation: 2 additional spaces. - Reference files, modules, functions, or symbols in
backticks. - Quantify impact when supported by the diff or context (e.g. lines removed, build time).
Trailers
- Do not add Co-Authored-By, Signed-off-by, or other trailers unilaterally. Include only when the user or environment explicitly requests them.
- Place trailers after a blank line following the body (or subject if no body).
- ASCII-only rule applies to trailers.
Contextual logic
- Infer the primary intent from the diff (e.g. "Extract hook", "Replace duplicated logic", "Standardize scripts").
- Do not invent issue IDs, performance numbers, or behavior claims not evident from the diff or context.
- If no issue ID is provided, omit the footer entirely.
Multi-concern diffs
When a diff spans multiple unrelated concerns (e.g. a refactor + a new feature + a typo fix):
- Flag it: Tell the user the diff contains distinct concerns and suggest splitting into separate commits.
- If the user wants one commit: Use the primary change as the subject. Use labeled sections in the body to cover secondary concerns.
- If the user wants to split: Suggest which files or hunks belong to which commit.
Anti-patterns
- Do not generate a message and then immediately run
git commitunless the user explicitly asked you to commit. - Do not invent issue IDs or claim behavior changes not supported by the diff.
- Do not add trailers (Co-Authored-By, etc.) unless explicitly requested.
Examples
Simple (no body):
Fix typo in READMEWith body:
Extract WebSocket connection logic into hook
This commit moves WebSocket connection management from the
component into a reusable hook. This reduces duplication
across three components and makes testing easier.
- Extract `useWebSocket` hook from `ChatComponent`
- Update `SessionComponent` and `BuilderComponent` to use hook
- Add unit tests for hook behaviorWith issue reference:
Add runtime startup validation
This commit adds validation to ensure the runtime container
starts correctly before accepting connections. Prevents
cascading failures when the runtime is misconfigured.
Fixes:
- Runtime crashes on invalid environment variables
- Silent failures when Docker image is missing
Closes #123Related skills
- Run
/verify-changesbefore generating a commit message to ensure the build passes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

