batch-commit
Skill1 starsChanged 4 days agoMITView on GitHub
Groups uncommitted changes into logical batches, stages each batch with git add, and provides a one-liner commit message for each. Use when there are many changed files that should be committed as separate logical units.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Wanghaoyihaoyi/agent-skillstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Wanghaoyihaoyi/agent-skills★ 3same name
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 repository21 other files it gives its agents.
- animation-vocabularySkill
- apple-chartsSkill
- apple-hig-componentsSkill
- apple-hig-foundationsSkill
- apple-hig-getting-startedSkill
- apple-hig-inputsSkill
- apple-hig-patternsSkill
- apple-hig-technologiesSkill
- apple-sheetsSkill
- fluid-interface-designSkill
- git-change-controlSkill
- improve-animationsSkill
- marketing-art-directionSkill
- marketing-product-mediaSkill
- marketing-reference-forensicsSkill
- marketing-visual-qaSkill
- message-delivery-integritySkill
- production-verificationSkill
- product-marketing-personasSkill
- security-auditSkill
- systems-builder-writingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
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 12
Run git status --short and git diff --stat HEAD to understand all pending changes.
- Distinctive: line 13
Read the changed files and relevant repository instructions to understand what each change does.
- Distinctive: line 26
NEVER run git commit yourself — only git add
- Distinctive: line 27
NEVER stage files outside the agreed batch (no git add .
- Distinctive: line 28
Prefer path-specific or patch-mode staging when a file contains unrelated changes.
- Very specific: line 30
Keep commit messages concise: <scope>: <what changed> format
- Distinctive: line 32
If a file has changes that belong to multiple batches, put it in the batch where its primary change belongs
- Distinctive: line 34
If there are only 1-3 related files, just stage them all as one batch — don't over-split
- Distinctive: line 38
Follow the project's existing commit style.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Batch Commit
Groups uncommitted changes into logical batches and stages them one at a time, providing a commit message for each.
Process
- Run
git status --shortandgit diff --stat HEADto understand all pending changes. - Read the changed files and relevant repository instructions to understand what each change does.
- Group related changes into logical batches (typically 3-7 batches). Group by:
- Feature/purpose: files that work together for the same feature
- Layer: infrastructure, services, UI, config, tests
- Type of change: new files, bug fixes, refactors
- Present ALL batches as a numbered summary with:
- The files in each batch
- A one-liner commit message
- Stage the first batch with explicit paths or hunks.
- Show the staged diff and wait for the user to commit, then stage the next batch when asked.
Rules
- NEVER run
git commityourself — onlygit add - NEVER stage files outside the agreed batch (no
git add .orgit add -A). - Prefer path-specific or patch-mode staging when a file contains unrelated changes.
- Inspect
git diff --cached --checkandgit diff --cachedbefore handing off a batch. - Keep commit messages concise:
<scope>: <what changed>format - Order batches so foundational changes come first (infra before features, libraries before consumers)
- If a file has changes that belong to multiple batches, put it in the batch where its primary change belongs
- Exclude files that look like they shouldn't be committed (
.env, secrets, temp files) and flag them to the user - If there are only 1-3 related files, just stage them all as one batch — don't over-split
Commit Message Style
Follow the project's existing commit style. If no clear style exists, use:
<scope>: <short imperative description>Examples:
api: add authenticated client token bridgebilling: fix invoice pagination response shapedocs: update deployment guide for new environment variables
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.

