gh-commit
Skill3 starsChanged 33 days agoMITView on GitHub
Create atomic commits in the conventional format. Use when the user asks to commit or save changes.
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- bastani-inc/atomictheir own version, first seen Oct 8, 2026
- nrjdalal/zerostarteredited, first seen Oct 8, 2026
- flora131/atomictheir own version, first seen Oct 8, 2026
- kelvincushman/orphustheir own version, first seen Jul 30, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- nrjdalal/zerostarter★ 6597% same
Wrote their own version · 3
- bastani-inc/atomic★ 881same name
- flora131/atomic★ 881same name
- kelvincushman/orphus★ 4same 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.
- AGENTS.mdAGENTS.md
- add-packageSkill
- agent-browserSkill
- api-endpointSkill
- auditSkill
- codebase-mapSkill
- db-migrationSkill
- designSkill
- devSkill
- docker-testSkill
- doc-syncSkill
- fontsSkill
- iceboxSkill
- ignore-syncSkill
- portlessSkill
- releaseSkill
- runtime-apisSkill
- shadcn-syncSkill
- shipSkill
- skills-managerSkill
- ui-verifySkill
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 4 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
- Distinctive: line 22
Read the staged and unstaged changes before deciding what belongs together.
- Very specific: line 45
Never add Co-authored-by (repo rule).
- Distinctive: line 59
Stop after the commit. Push only when the user says "commit and push", "push the changes", or confirms when asked.
- Distinctive: line 63
Never commit directly to canary (the default branch).
“Common” is measured: kept by at least 6 in 10 of the 4 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
[!CAUTION] Synced from https://github.com/nrjdalal/zerostarter. Customize this skill or remove this note to stop syncing.
Git Commit
ATOMIC commits, conventional format. Stage and commit only; never push unless the user explicitly asks.
1. Inspect
git status --short
git diff
git diff --stagedRead the staged and unstaged changes before deciding what belongs together.
2. Stage
One logical unit per commit (ATOMIC): split unrelated changes into separate commits so every staged file belongs to the same unit.
git add <paths>3. Commit
git commit -m "<type>(<scope>): <subject>"| Element | Rule |
| Type | feat, fix, refactor, docs, chore, test, perf, style, build, revert. Type ci is RESERVED for pipeline-generated commits (ci(changelog), ci(version)) and dropped from the changelog (changelog.config.json); real CI work uses fix(ci)/feat(ci)/docs(ci). Dependency refreshes use build(deps), never chore(deps): changelogen hardcodes dropping non-breaking chore(deps) from the changelog, so a release window holding only one can never release (v0.1.25's notes silently lost the cn + zod bump this way). |
| Scope | Optional area in parentheses (package, component, feature). |
| Subject | Imperative, lowercase, no period. The commit-msg hook rejects a header over 100 chars or a capitalized subject (subject-case). |
| Body | Optional; explain "why", not "what". Wrap lines at 100 (the hook rejects longer). |
Never add Co-authored-by (repo rule). The commit-msg hook runs commitlint (@commitlint/config-conventional); pre-commit regenerates the AGENTS.md skills tables when a skill changed, then runs lint-staged, then bun run build.
Examples:
feat(auth): add OAuth provider support
fix(api): prevent duplicate webhook delivery
refactor(web): extract auth middleware into separate module
docs(readme): update installation steps
build(deps): bump dependencies to latest versions4. Push (only when explicitly requested)
Stop after the commit. Push only when the user says "commit and push", "push the changes", or confirms when asked.
Notes
- Never commit directly to canary (the default branch); branch first, then PR.
- The pre-commit build prints the size table only. Refresh the graph svg manually:
bun .github/scripts/build-sizes.ts --graph.
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.