commit
Skill2 starsChanged 5 days agoMITView on GitHub
Commit changes with an auto-generated message. Stages all uncommitted files and commits with a concise summary.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- 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
Used with
Projects with it also use act-on-feedback, generate-run-commands 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.
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 4 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 4 projects that use this
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
MindgamesSkillbranch
Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.
Also in 9 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
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
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- microsoft/vscode★ 195ksame name
- TryGhost/Ghost★ 56ksame name
- ToolJet/ToolJet★ 41ksame name
- ShareX/ShareX★ 41ksame name
- openai/symphony★ 27ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- windmill-labs/windmill★ 19ksame name
- EverMind-AI/EverMemOS★ 14ksame name
- EverMind-AI/EverOS★ 14ksame name
177 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 repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- 1passwordSkill
- brainSkill
- brainstormSkill
- bridgeSkill
- claude-switcherSkill
- clear-cacheSkill
- cross-artifactSkill
- ctoSkill
- diskSkill
- killSkill
- lookSkill
- parseSkill
- pbarSkill
- planSkill
- pruneSkill
- pushSkill
- reportSkill
- researchSkill
- swarmSkill
- vibe-auditSkill
- video-editorSkill
- webSkill
- wikiSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Before staging, run the sidecar script if sqlite_tracking is configured in .claude/kit.json:
- Distinctive: line 42
Read the optional author override first — it applies to all modes:
- Distinctive: line 47
Default (all uncommitted files):
- Very specific: line 61
After committing, push the named subtree to its deploy repo.
- Very specific: line 83
If the name is not found in subtrees, list available names and ask the user.
- Very specific: line 100
When the key is absent — or there is no kit.json at all — commits use the repo's git config as normal.
- Very specific: line 119
If .claude/kit.json has a rules."commit" entry, read it and apply it as an additional instruction for this skill.
“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 Changes
Commits uncommitted files with an auto-generated commit message.
Modifiers
/commit— Default. Stages and commits all uncommitted files in the project./commit only— Stages and commits only files modified during the current session./commit sub <name>— Commits all changes, then pushes the named subtree to its deploy repo.
Input
Optional argument: $ARGUMENTS
Procedure
- Determine scope based on modifier (default = all, "only" = session files, "sub" = all + subtree push)
- Run
git statusto see what's uncommitted Regenerate SQLite sidecars (if configured)
Before staging, run the sidecar script if
sqlite_trackingis configured in.claude/kit.json:bash ~/.claude-kit/scripts/sqlite-sidecar.shThe script is a no-op if no
sqlite_trackingis configured in.claude/kit.json. See the script header for config format.- Generate commit message summarizing the changes
Stage and commit
Read the optional author override first — it applies to all modes:
AUTHOR=$(jq -r '.commit.author // empty' .claude/kit.json 2>/dev/null)Default (all uncommitted files):
git add -A [ -n "$AUTHOR" ] && git commit --author="$AUTHOR" -m "<message>" || git commit -m "<message>"With "only" modifier (session files only):
git add <file1> <file2> ... [ -n "$AUTHOR" ] && git commit --author="$AUTHOR" -m "<message>" || git commit -m "<message>"Subtree push (only with
submodifier)After committing, push the named subtree to its deploy repo. Read the subtree config from
.claude/kit.json:{ "subtrees": { "app": { "prefix": "app", "remote": "app", "branch": "main" } } }Resolve the subtree name from the argument:
PREFIX=$(jq -r ".subtrees.\"$NAME\".prefix" .claude/kit.json) REMOTE=$(jq -r ".subtrees.\"$NAME\".remote" .claude/kit.json) BRANCH=$(jq -r ".subtrees.\"$NAME\".branch // \"main\"" .claude/kit.json)If the name is not found in
subtrees, list available names and ask the user.Then push:
git subtree push --prefix="$PREFIX" "$REMOTE" "$BRANCH"Report success and the remote URL.
Author override
A project may pin the commit author in .claude/kit.json:
{ "commit": { "author": "Jane Dev <jane@example.com>" } }When the key is absent — or there is no kit.json at all — commits use the repo's git config as
normal. This is the common case; most projects should not set it.
--authorsets the author only. The committer still comes from git config, so an override produces a commit whose two identities differ. That is usually what's wanted. If both must match, setGIT_AUTHOR_NAME/GIT_AUTHOR_EMAIL/GIT_COMMITTER_NAME/GIT_COMMITTER_EMAILin the environment instead — the flag cannot do it.
Rules
- No permission required - Execute immediately without asking
- Concise messages - Summarize what changed, not every detail
- Never be selective - In default mode, commit everything without question. Do not skip log files, generated files, or any other files.
git add -Ameans everything. - Never skip hooks (
--no-verify)
Project overrides
If .claude/kit.json has a rules."commit" entry, read it and apply it as an additional
instruction for this skill. Absent file or key means no overrides — that is the normal case.
jq -r '.rules."commit" // empty' .claude/kit.json 2>/dev/nullDoes 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.

