commit
Skill1 starsChanged 13 days agoApache-2.0View on GitHub
Stage and commit work without pulling in unrelated changes. Use whenever committing, staging, amending, or moving changed files into a worktree, and when the user says "commit only what you changed".
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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-chatSkill
- argocdSkill
- code-reviewSkill
- dependency-trackSkill
- financeSkill
- handoffSkill
- java-21-to-25-migrationSkill
- jenkinsSkill
- jiraSkill
- perplexitySkill
- pr-readySkill
- researchSkill
- shipSkill
- skanetrafikenSkill
- sonarqubeSkill
- tddSkill
- to-tasksSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
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 16
Never git add -A, git add ., git add -u, or git commit -a.
- Very specific: line 24
Never stage implementation-notes-*.md.
- Distinctive: line 33
No file-by-file summary, no filenames, no implementation narration.
- Distinctive: line 34
No separate "Why" section.
- Very specific: line 36
No AI, agent, model, or provider attribution.
- Distinctive: line 38
No employer name, personal name, or email.
- Distinctive: line 44
No secrets, keys, tokens, or customer data in the diff.
“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
The working tree usually contains work that is not yours. Staging is an explicit act.
Stage only your own edits
git status --porcelainandgit diff --statfirst. Read the whole list.- Identify the files you edited this session. If unsure which those are, say so and ask rather than guessing.
- Stage them by explicit path:
git add path/a path/b. - Never
git add -A,git add .,git add -u, orgit commit -a. git diff --cachedbefore committing. If anything in it is not yours, unstage it.
Untracked files are not automatically yours and are not automatically disposable.
The same rule applies when moving work into a worktree: carry over the files you changed, not everything the tree shows as dirty.
Never stage implementation-notes-*.md. It is a local record, not part of the change.
Write the message
Conventional Commits: type(scope): intent. Types: feat, fix, refactor, test, docs,
build, ci, chore, perf, revert.
- Three sentences maximum, total.
- Say why the change exists and what outcome it achieves.
- No file-by-file summary, no filenames, no implementation narration.
- No separate "Why" section.
- No em dashes.
- No AI, agent, model, or provider attribution. No
Co-Authored-By, no session trailers, no session links. If a tool adds one, remove it before committing. - No employer name, personal name, or email.
Before the commit lands
- The relevant tests were run and passed. Not "should pass".
- The staged diff contains only intended changes.
- No secrets, keys, tokens, or customer data in the diff.
- Generated files in the diff are there on purpose.
Never without being asked
Amend, squash, rebase, reset --hard, force-push, or rewrite history. Each needs
explicit approval naming what will be rewritten.
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.