commit
Skill166 starsChanged 5 months agoMITView on GitHub
Stage and commit with flexible intent parsing. Accepts file/folder scope, free-text description, amend, or any combination.
- Reads credentials
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
- ryoppippi/ccusage★ 19ksame name
- ccusage/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 repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/qmd-search.mdcCursor rule
- .cursor/rules/skill-conventions.mdcCursor rule
- .cursor/rules/skill-registry.mdcCursor rule
- cache-notesSkill
- defuddleSkill
- fill-participantsSkill
- followup-todosSkill
- json-canvasSkill
- last-1on1Skill
- mail-transcriptsSkill
- meetingSkill
- migrate-tagsSkill
- note-statusSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- onboard-personSkill
- organize-meetingsSkill
- otter-fetchSkill
- people-stubsSkill
- qmdSkill
- recapSkill
- sprint-retroSkill
- sync-upstream-obsidianosSkill
- vault-healthSkill
- workspace-modeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 11 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
4
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
- Very specific: line 26
Amend flag: If the first word is amend, set amend mode and strip it.
- Distinctive: line 29
Nothing: No arguments at all — default mode.
- Distinctive: line 66
If nothing matches (no changes in scope, or no related files for intent), tell the user and stop.
- Distinctive: line 70
If the file set is already fully staged, skip.
- Very specific: line 71
If unrelated files are staged, unstage them first (git restore --staged <path>).
- Distinctive: line 81
If the user provided intent, use it to guide the message but still ground it in the actual diff.
- Distinctive: line 89
Wait for user confirmation before proceeding.
- Distinctive: line 100
Before amending, verify ALL of these conditions:
- Distinctive: line 106
If any condition fails, refuse and explain why.
- Very specific: line 110
When called as part of a sequenced workflow (e.g.
- Distinctive: line 116
When committing on behalf of a sequence:
- Distinctive: line 125
Always use explicit file paths for staging — never broad patterns.
- Distinctive: line 126
If no files were actually modified, skip the commit offer.
- Very specific: line 127
Never commit files that likely contain secrets (.env, credentials, tokens).
- Distinctive: line 128
When the scope is a folder, include all changed files recursively under it.
“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
Usage
| Command | What it does |
/commit | Commit staged files; if none staged, infer related changes |
/commit <file> | Scope to a specific file's changes |
/commit <folder>/ | Scope to a folder's changes |
/commit <description> | Infer scope from free-text intent |
/commit <scope> <description> | Scope + explicit intent |
/commit amend | Amend the last commit (re-use message) |
/commit amend <scope/description> | Amend with additional scope or new message |
| (sequence mode) | Deferred — sub-skills skip, caller commits once at the end |
Argument Parsing
Parse the raw argument string into scope, intent, and flags:
- Amend flag: If the first word is
amend, set amend mode and strip it. The remainder is parsed normally. - Scope (file or folder): Any token that matches a real path in the repo (file or directory) — whether provided via
@-reference or plain text. Multiple scopes are allowed. - Intent (free-text description): Whatever remains after extracting scopes. Used to guide the commit message.
- Nothing: No arguments at all — default mode.
Examples:
| Input | Scope | Intent | Amend |
| (empty) | — | — | no |
Meetings/Engineering/ | Meetings/Engineering/ | — | no |
.gitignore | .gitignore | — | no |
my awesome refactor | — | my awesome refactor | no |
Meetings/ wrap up notes | Meetings/ | wrap up notes | no |
amend | — | — | yes |
amend .obsidian/ | .obsidian/ | — | yes |
amend fixed typo | — | fixed typo | yes |
Workflow
1. Gather state
Run in parallel:
git diff --staged --stat— staged changesgit diff --stat— unstaged changesgit status --short— untracked filesgit log --oneline -5— recent commits (for style and amend safety)
2. Determine file set
Resolve which files will be committed, based on parsed arguments:
| Scenario | File set |
| Scope provided | Only changed/untracked files under the given path(s). Ignore everything else. |
| Intent provided, no scope | Analyze all changed files; select only those whose diffs relate to the described intent. Present the selection for confirmation. |
| No args + staged files exist | Use exactly what's staged. Do NOT add unstaged files — the user intentionally staged those. |
| No args + nothing staged | Analyze all changed/untracked files. Group related changes and propose a sensible set. Ask for confirmation. |
If nothing matches (no changes in scope, or no related files for intent), tell the user and stop.
3. Stage files
- If the file set is already fully staged, skip.
- If unrelated files are staged, unstage them first (
git restore --staged <path>). - Stage the resolved file set with explicit paths — never broad patterns.
4. Craft the commit message
Analyze the staged diff (git diff --staged) and write:
- Title: ≤72 chars, conventional format —
type: summary.- Common types:
add(new files),update(modify existing),fix(corrections),chore(config/tooling),feat(new capability),refactor,docs,rename.
- Common types:
- Body (optional): 1–3 lines explaining "why" if not obvious. Omit for trivial changes.
- If the user provided intent, use it to guide the message but still ground it in the actual diff.
5. Present and confirm
Show:
- The list of files that will be committed (or amended).
- The proposed commit message.
Wait for user confirmation before proceeding.
6. Commit
- Normal mode:
git commitwith the confirmed message. - Amend mode:
git commit --amend(see safety rules below). If the user provided new intent, replace the message; otherwise keep the existing message (--no-edit).
Do not push.
Amend Safety
Before amending, verify ALL of these conditions:
- HEAD was created by you in this conversation — check
git log -1. - HEAD has not been pushed —
git statusshould show "Your branch is ahead" or the commit should not exist on the remote. - The user explicitly said
amend.
If any condition fails, refuse and explain why. Suggest creating a new commit instead.
Sequence Mode
When called as part of a sequenced workflow (e.g. /meeting wrap), the caller owns the commit. Individual sub-skills skip their commit step.
How to detect: the calling workflow explicitly states it is running sub-skills in sequence. Do not offer to commit — just proceed. The sequence owner commits once at the end with a combined message.
Sub-skill commit format
When committing on behalf of a sequence:
- Message:
update: /{workflow-name} {argument}(e.g.update: /meeting wrap Meetings/Engineering/Some Meeting.md). - Stage only files modified by the current skill invocation (or full sequence). Use explicit paths.
- Present and confirm before committing.
Important Notes
- This workspace may not be a git repo. If
git statusfails, skip entirely without error. - Always use explicit file paths for staging — never broad patterns.
- If no files were actually modified, skip the commit offer.
- Never commit files that likely contain secrets (
.env, credentials, tokens). - When the scope is a folder, include all changed files recursively under 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.

