commit
Skill893 starsChanged yesterdayBSD-3-ClauseView on GitHub
Stage and commit all changes in this repo
187 other projects use a version of this.
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 · 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.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 5 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
If the user passed an argument, it can hold commit details, instructions, or both:
- Distinctive: line 14
Do the following steps in order:
- Distinctive: line 16
Run git status to see what's modified
- Very specific: line 17
Run git add -A to stage everything (.gitignore already excludes transient runtime files)
- Distinctive: line 18
If there is nothing to stage, say so clearly and stop — do not create an empty commit
- Very specific: line 19
Write a commit message that summarizes the recent work to a temp file, then run git commit -F <tempfile> and delete the temp file afterward.
- Distinctive: line 20
Do NOT use git commit -m — multi-line messages with special characters break shell quoting.
- Very specific: line 21
Do NOT use heredoc syntax (<< 'EOF') — it interacts badly with some agents' terminal tools.
- Very specific: line 22
Instead, use printf to write the temp file, one 'line' argument per line:
- Very specific: line 28
If commit details were provided (e.g.
- Very specific: line 32
Only push if the user asked to (e.g.
“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
You are performing a git commit for this repo.
If the user passed an argument, it can hold commit details, instructions, or both:
- Commit details (e.g.
closes #123) go in the commit message, as described in step 4. - Instructions (e.g.
and push,only the README changes) are for you to follow. Don't put them in the commit message.
Do the following steps in order:
- Run
git statusto see what's modified - Run
git add -Ato stage everything (.gitignorealready excludes transient runtime files) - If there is nothing to stage, say so clearly and stop — do not create an empty commit
- Write a commit message that summarizes the recent work to a temp file, then run
git commit -F <tempfile>and delete the temp file afterward.- Do NOT use
git commit -m— multi-line messages with special characters break shell quoting. - Do NOT use heredoc syntax (
<< 'EOF') — it interacts badly with some agents' terminal tools. - Instead, use
printfto write the temp file, one'line'argument per line:printf '%s\n' 'First line' '' 'Second line' 'Third line' > /tmp/commitmsg.txt git commit -F /tmp/commitmsg.txt rm -f /tmp/commitmsg.txt - If commit details were provided (e.g.
closes #123), include them on their own line after the first line (subject), separated by a blank line:printf '%s\n' 'First line' '' 'closes #123' > /tmp/commitmsg.txt
- Do NOT use
- Only push if the user asked to (e.g.
/commit and push). Otherwise stop after committing, so the user can review or amend the commit first.
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.

