commit
Skill0 starsChanged 5 months agoMITView on GitHub
Commit guidelines. Use when the user asks to commit, stage changes, or says "commit this", "commit my work", "save my progress", "commit what we did". Triggers on "commit", "git commit", "stage and commit", "save progress".
- 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 repository18 other files it gives its agents.
- app-icon-gridSkill
- archive-manualSkill
- component-consistencySkill
- component-locatorSkill
- debug-triageSkill
- gemini-iconSkill
- parity-auditorSkill
- prd-writingSkill
- refactor-and-safety-passSkill
- release-helperSkill
- smellSkill
- streamdeck-aerospace-rewireSkill
- streamdeck-workspace-buttonSkill
- svg-icon-renderSkill
- test-conventionsSkill
- verification-gateSkill
- work-breakdownSkill
- yt-audioSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
8
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 14
Run git status and git diff first to see everything that's changed.
- Distinctive: line 17
If there are unrelated changes in the working tree, leave them unstaged.
- Distinctive: line 18
If unsure whether a file is related, ask the user before staging it.
- Distinctive: line 22
Write a concise message (1-2 sentences) that describes the why, not just the what.
- Very specific: line 28
Do not commit files that contain secrets (.env, credentials, API keys, tokens).
- Very specific: line 29
Do not commit debugging artifacts (console.log added during the session, debugger statements).
- Distinctive: line 30
Do not commit commented-out code that was disabled during debugging.
- Distinctive: line 31
If a pre-commit hook fails, fix the issue and create a new commit — never amend the previous commit unless the user explicitly asks.
- Distinctive: line 35
Never group unrelated work into one commit: If the user worked on feature A and there are also leftover changes from feature B, only commit …
- Distinctive: line 36
Never auto-push: Only push if the user explicitly asks.
“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
You are committing code changes. Follow these rules strictly.
Only Commit Relevant Changes
This is the most important rule: only stage files that are directly related to the work just completed.
- Run
git statusandgit difffirst to see everything that's changed. - Identify which files relate to the task you just worked on.
- Stage those files individually by name — never use
git add -A,git add ., orgit add --all. - If there are unrelated changes in the working tree, leave them unstaged. Do not bundle them in.
- If unsure whether a file is related, ask the user before staging it.
Commit Message
- Write a concise message (1-2 sentences) that describes the why, not just the what.
- Match the style of recent commits in the repo (
git log --oneline -10). - End with the co-author trailer.
Pre-Commit Checks
- Do not commit files that contain secrets (
.env, credentials, API keys, tokens). - Do not commit debugging artifacts (
console.logadded during the session,debuggerstatements). - Do not commit commented-out code that was disabled during debugging.
- If a pre-commit hook fails, fix the issue and create a new commit — never amend the previous commit unless the user explicitly asks.
What NOT to Do
- Never group unrelated work into one commit. If the user worked on feature A and there are also leftover changes from feature B, only commit feature A.
- Never auto-push. Only push if the user explicitly asks.
- Never amend unless the user explicitly says "amend".
- Never use
--no-verifyunless the user explicitly asks.
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.