commit-message
Skill1 starsChanged 53 days agoMITView on GitHub
Propose a git commit message using conventional commits format (feat:, fix:, refactor:, etc.) based on staged/unstaged changes. Always in English. Never commit without explicit user approval.
62 other projects use a version of this.
Adopted by
Most recently taken up by
- AcademySoftwareFoundation/OpenImageIOtheir own version, first seen Nov 9, 2026
- haiderstudio/commit-message-skilltheir own version, first seen Nov 8, 2026
- mab-go/xmind-mcptheir own version, first seen Nov 8, 2026
- danielvm-git/bigpowerstheir own version, first seen Nov 6, 2026
- drinkspiller/skillstheir own version, first seen Nov 6, 2026
- mattiacerutti/supernovatheir own version, first seen Nov 2, 2026
Used with
Projects with it also use pr-description, changelog 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 9 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 3 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
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 7 projects that use this
- GoogleSkill
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Also in 3 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 3 projects that use this
- +2 more from google
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- 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
- sheshbabu/zen★ 1.2ksame name
- s-kostyaev/ellama★ 963same name
- tektoncd/operator★ 606same name
- danielvm-git/bigpowers★ 288same name
- rshdhere/vibecheck★ 213same name
52 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 repository28 other files it gives its agents.
- journal-coachSkill
- github-templatesSkill
- node-ciSkill
- renovateSkill
- create-readmeSkill
- markdown-styleSkill
- mermaid-syntaxSkill
- obsidian-vaultSkill
- ste100Skill
- forge-detectSkill
- forgejo-issueSkill
- forgejo-prSkill
- web-frontendSkill
- docker-pythonSkill
- pyproject-tomlSkill
- python-ciSkill
- python-cliSkill
- python-devcontainerSkill
- python-projectSkill
- architecture-briefSkill
- design-advisorSkill
- saas-anti-pattern-reviewSkill
- saas-transition-chain-reviewSkill
- saas-transition-reviewSkill
- saas-transition-strategySkill
- security-reviewerSkill
- technical-debt-reviewSkill
- discord-sendSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
When the user asks you to suggest or propose a commit message, follow this workflow.
- Distinctive: line 18
If empty, fall back to:
- Distinctive: line 24
If both are empty, inform the user and stop.
- Distinctive: line 50
Never commit automatically: Only run git commit if the user explicitly says to (e.g.
- Distinctive: line 54
If the user asks for adjustments, incorporate the feedback and re-propose.
“Common” is measured: kept by at least 6 in 10 of the 51 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
When the user asks you to suggest or propose a commit message, follow this workflow.
1. Detect changes
git diff --cachedIf empty, fall back to:
git diffIf both are empty, inform the user and stop.
2. Analyze the diff
Determine these four parts:
| Part | Rules |
| Type | One of feat, fix, refactor, docs, style, test, chore, perf, ci, build, revert. Prefer feat/fix unless the change is clearly neither. |
| Scope (optional) | The module or area affected. Infer from file paths (e.g. auth, expenses, ui, backend, frontend). |
| Short description | Imperative present tense, lowercase, no trailing period, max 72 characters. |
| Body (optional) | Blank line followed by bullet points or short paragraphs explaining motivation and context. Wrap at 72 characters. |
3. Propose
Present the message in a code block. Ask the user:
- Use as-is?
- Edit it (adjust type / scope / description)?
- Reject and start over?
4. Commit only on explicit approval
git commit -m "type(scope): description" -m "body line 1\nbody line 2"Never commit automatically. Only run git commit if the user explicitly says to (e.g. "yes, commit it", "go ahead").
5. Iterate
If the user asks for adjustments, incorporate the feedback and re-propose.
Examples
feat(auth): add force password change on first loginfix(expenses): prevent division by zero in split calculation
The split amount formula divided by participant count without
checking for zero, causing a 500 error when removing all
participants.refactor(api): extract validation logic into reusable helpersdocs: update API endpoint list in architecture.mdDoes 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.