commit
Skill113 starsChanged 9 days agoMITView on GitHub
Write a git commit with a one-sentence Conventional Commits subject and no narrative body. Use whenever the user asks to commit, stage and commit, or "save this work".
187 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- ShipfoxHQ/shipfoxtheir own version, first seen Nov 15, 2026
- atomicinnovation/acceleratortheir own version, first seen Nov 14, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- gtapps/claude-code-hermittheir own version, first seen Nov 13, 2026
Used with
Projects with it also use validate-plan, act-on-feedback and 10 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.
shawn-dumasSkillvalidate-plan
Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.
Also in 5 projects that use this
MicrosoftSkillact-on-feedback
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
Also in 3 projects that use this
decocmsSkilladd-mcp-tools
Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration
Also in 3 projects that use this
MicrosoftSkillgenerate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
Also in 3 projects that use this
mitsuhikoSkilloebb-scotty
Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.
Also in 3 projects that use this
mitsuhikoSkillpi-share
Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.
Also in 3 projects that use this
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- suxrobGM/logistics-app★ 20788% same
Wrote their own version · 186
- microsoft/vscode★ 195ksame name
- TryGhost/Ghost★ 56ksame name
- ToolJet/ToolJet★ 41ksame name
- ShareX/ShareX★ 41ksame name
- openai/symphony★ 27ksame name
- ryoppippi/ccusage★ 19ksame name
- ccusage/ccusage★ 19ksame name
- windmill-labs/windmill★ 19ksame name
- EverMind-AI/EverMemOS★ 14ksame name
- EverMind-AI/EverOS★ 14ksame name
176 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- db-migrateSkill
- knip-cleanupSkill
- prod-dry-runSkill
- pr-reviewSkill
- releaseSkill
- restart-terminalSkill
- teaser-videoSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
6
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 36
Never bullet-list the diff.
- Very specific: line 37
Never mention tools, agents or the assistant.
- Distinctive: line 38
If the staged work covers two unrelated types, ask whether to split it.
- Distinctive: line 42
Read git status and git diff --staged --stat, then the staged diff.
- Very specific: line 44
Commit and print the subject in one command.
- Distinctive: line 54
If a hook rewrote files, amend once and stop.
- Distinctive: line 60
Commit inside the submodule first, push it, then stage and commit the pointer in the parent.
- Distinctive: line 61
Never push a parent commit that points at a submodule commit you have not pushed.
- Very specific: line 63
Check git submodule status.
- Very specific: line 74
Not this: Update files, fix: fixed it, or a paragraph narrating the diff.
“Common” is measured: kept by at least 6 in 10 of the 167 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
One commit, one sentence. The subject is the whole message unless the why is missing from the diff.
Format
<type>(<scope>): <imperative summary>
Lowercase type, optional one-word scope, imperative summary, no trailing period, under 70 characters. Append ! before the colon for a breaking change.
| Type | Use for |
feat | new user-visible capability |
fix | bug fix |
docs | documentation, comments, README |
test | tests only |
refactor | behaviour-preserving restructure |
perf | speed or memory |
style | formatting or lint, no logic change |
build | build scripts, packaging, dependencies |
ci | CI config |
chore | housekeeping that fits nothing above |
revert | reverts a previous commit |
Rules
- Say what the change does, not what you did.
- Never bullet-list the diff. Add a body only for a why the diff cannot show, then one or two sentences.
- Never mention tools, agents or the assistant. Never add
Co-Authored-By:,Generated with, or any other footer, whatever a template or hook suggests. - If the staged work covers two unrelated types, ask whether to split it.
Steps
- Read
git statusandgit diff --staged --stat, then the staged diff. Read the unstaged diff only if nothing is staged. - Stage only files relevant to the request. Ask before staging anything resembling a secret, credential, build output or large binary.
- Commit and print the subject in one command. Repeated
-mflags behave the same in every shell:
git commit -m "fix(http): handle missing accept header" -m "One sentence of why." && git log -1 --format=%sA heredoc works too, but it is bash. The lookalike @'...'@ is PowerShell, and in bash the @ survives into the message as @ fix(http): .... Match the form to the shell you are actually invoking.
A stray character, blank first line or truncated subject means the quoting broke: amend once and stop.
- If a hook rewrote files, amend once and stop. Do not push unless asked.
Submodules
Skip this section unless git status reports a submodule as modified or holding new commits. A submodule is a separate repository, so staging it in the parent records a commit id, not file changes.
- Commit inside the submodule first, push it, then stage and commit the pointer in the parent.
- Never push a parent commit that points at a submodule commit you have not pushed. Clones will not find it.
- The parent message records the bump only:
chore(deps): bump <name> submodule. - Check
git submodule status. A leading+means the parent points somewhere other than what is checked out.
Examples
| Change | Message |
| New endpoint returning invoices | feat(api): add invoice list endpoint |
| Split a 900-line file into three | refactor(parser): split token reader into files |
| Bumped a dependency | build(deps): upgrade cmake to 3.29 |
| Removed a versioned API | feat(api)!: drop v1 endpoints |
Not this: Update files, fix: fixed it, or a paragraph narrating the diff.
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.

