commit
Skill1 starsChanged 2 months agoMITView on GitHub
Use when the user asks to commit, to create a pull request, or when a change is verified and ready to land - produces atomic commits that stage only the files belonging to the change, with a message and PR body written from the actual diff.
- Reads credentials
188 other projects use a version of this.
Adopted by
Most recently taken up by
- daledesilva/obsidian_inktheir own version, first seen Nov 9, 2026
- thoughtbot/rails-consultanttheir own version, first seen Nov 8, 2026
- pedrohcgs/claude-code-my-workflowtheir own version, first seen Nov 8, 2026
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- denysdovhan/skillstheir own version, first seen Nov 8, 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
- MicrosoftSkill
generate-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
- mitsuhikoSkill
pi-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 versions188 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 188
- 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★ 18ksame name
- EverMind-AI/EverMemOS★ 14ksame name
- EverMind-AI/EverOS★ 14ksame name
178 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-reviewSkill
- architecture-guidelinesSkill
- auto-run-taskSkill
- code-auditingSkill
- enrich-taskSkill
- harness-setupSkill
- run-taskSkill
- runtime-verificationSkill
- start-projectSkill
- update-docsSkill
- using-git-worktreesSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
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 14
Never commit unrelated work: Run git status first. If the tree contains modifications outside the change, list them to the user and stage …
- Very specific: line 17
Never commit secrets or local config: Check the diff for keys, tokens, .env values and absolute paths from this machine before staging.
- Distinctive: line 42
Write the body from the diff you actually staged.
- Distinctive: line 47
When a PR is requested, the body carries:
“Common” is measured: kept by at least 6 in 10 of the 168 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
Rules
- Atomic. One commit per logical change. Never
git add -Aorgit add .; stage the specific paths this change touched. - Never commit unrelated work. Run
git statusfirst. If the tree contains modifications outside the change, list them to the user and stage only what belongs. Do not stash or revert someone else's work-in-progress. - Never commit secrets or local config. Check the diff for keys, tokens,
.envvalues and absolute paths from this machine before staging. - English, imperative mood, as required by the project language standard.
- Do not commit unless asked. The harness loop stops before delivery so the human reviews first.
Branch
Work on a feature branch, never directly on the default branch. These projects use
phase-based naming - follow whatever the repository already does (for example
phase-NN-<slug>), and if no convention is visible, ask instead of inventing one.
Message format
<type>: <what changed, imperative, under 72 chars>
<why it changed - the problem, not a restatement of the diff>
<what to know when reading it later: decisions taken, trade-offs,
what was deliberately left out>Types: feat, fix, refactor, test, docs, chore, perf.
Write the body from the diff you actually staged. Do not describe files you did not change, and do not claim tests pass unless you ran them in this session.
Pull request
When a PR is requested, the body carries:
- What - the behaviour change, in product terms.
- Why - the problem or the roadmap phase it belongs to.
- How - the approach and the decisions worth questioning.
- Verification - the commands actually run and their results, plus what was not covered.
- Risk - what could break, and the rollback.
Link the change artifacts (OpenSpec change folder, spec or ADR) rather than duplicating their content.
Before finishing
Report the commit hash and the exact paths staged, so the human can check nothing extra travelled with it.
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.