commit-helper
Skill1 starsChanged 40 days agoMITView on GitHub
Stages changes and writes a Conventional Commits message from the actual diff. Use when the user asks to commit, wants a commit message, or says "commit this".
10 other projects use a version of this.
Adopted by
Most recently taken up by
- aidankaokao/claude-skillstheir own version, first seen Oct 9, 2026
- chmouel/lazyworktreetheir own version, first seen Oct 8, 2026
- cockroachdb/cockroachtheir own version, first seen Oct 8, 2026
- 17-sss/agent-skillstheir own version, first seen Sep 22, 2026
- thinkmoon/commit-helper-skilltheir own version, first seen Jul 10, 2026
- almax000/claude-skillstheir own version, first seen Apr 19, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- cockroachdb/cockroach★ 33ksame name
- chmouel/lazyworktree★ 315same name
- nimbalyst/skills★ 28same name
- nodnarbnitram/claude-code-extensions★ 16same name
- peopleforrester/claude-dotfiles★ 3same name
- 17-sss/agent-skills★ 2same name
- almax000/claude-skills★ 1same name
- AntonioZS/claude-skills-mcp★ 1same name
- thinkmoon/commit-helper-skill★ 1same name
- aidankaokao/claude-skills★ 0same name
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 repository3 other files it gives its agents.
- bug-reportSkill
- code-reviewerSkill
- readme-writerSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 18
If nothing is staged and nothing is unstaged, tell the user there is nothing to commit and stop.
- Distinctive: line 20
If there are unstaged changes the user hasn't mentioned staging selectively, stage everything relevant with git add.
- Very specific: line 25
Write a commit message using Conventional Commits: <type>(<scope>): <short summary>
- Distinctive: line 31
If the change needs more explanation, add a blank line then 1-3 bullet points describing what and why (not a line-by-line diff narration).
- Very specific: line 33
Run git commit -m "...". Show the user the final message before or as part of the commit output.
- Distinctive: line 35
Never use git commit --amend or force-push unless the user explicitly asks for it — this skill only creates new commits.
“Common” is measured: kept by at least 6 in 10 of the 7 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 helper
Current state
- Status: !
git status --short - Staged diff: !
git diff --cached - Unstaged diff: !
git diff
Instructions
- If nothing is staged and nothing is unstaged, tell the user there is nothing to commit and stop.
- If there are unstaged changes the user hasn't mentioned staging
selectively, stage everything relevant with
git add. Ask first if the diff touches files that look unrelated to each other (e.g. an unrelated config file mixed in with feature code) — don't silently bundle unrelated changes into one commit. - Write a commit message using Conventional Commits:
<type>(<scope>): <short summary>- Types:
feat,fix,refactor,docs,test,chore,style,perf - Scope is optional; use it when the change is clearly limited to one module/feature.
- Summary is imperative mood, lowercase, no trailing period, under 72 chars.
- If the change needs more explanation, add a blank line then 1-3 bullet points describing what and why (not a line-by-line diff narration).
- Types:
- Run
git commit -m "...". Show the user the final message before or as part of the commit output. - Never use
git commit --amendor force-push unless the user explicitly asks for it — this skill only creates new commits.
Example
Diff shows a new rate limiter added to an API middleware file.
feat(api): add rate limiting to public endpoints
- caps requests per IP using a sliding window
- returns 429 with a Retry-After header when exceededDoes 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.