atomic-commits
Skill1 starsChanged 2 months agoMITView on GitHub
Create focused, working Git commits with Conventional Commits messages.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- gabrielbauman/skillstheir own version, first seen Nov 1, 2026
- arndvs/ctrlshfttheir own version, first seen Oct 15, 2026
- sergiooak/skillstheir own version, first seen Oct 9, 2026
- JohnnyMcGee/claude-skillstheir own version, first seen Oct 8, 2026
- ericmjl/skillstheir own version, first seen Sep 26, 2026
- definite-d/agent-skillstheir own version, first seen Jul 31, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- ericmjl/skills★ 41same name
- definite-d/agent-skills★ 2same name
- kutayilmaaz/agent-skills★ 2same name
- adambossy/skills★ 1same name
- bring-shrubbery/skills★ 1same name
- gabrielbauman/skills★ 1same name
- sergiooak/skills★ 1same name
- arndvs/ctrlshft★ 0same name
- dibenkobit/skills★ 0same name
- JohnnyMcGee/claude-skills★ 0same 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 repository16 other files it gives its agents.
- adversarial-refinement-loopSkill
- audio-verificationSkill
- build-without-fearSkill
- comfyui-assetsSkill
- diagnosing-bugsSkill
- finish-the-listSkill
- frontend-designSkill
- headless-terminal-workflowSkill
- parallelize-independent-workSkill
- prefer-second-monitorSkill
- require-external-communication-approvalSkill
- state-of-the-art-firstSkill
- try-it-firstSkill
- visual-verificationSkill
- web-design-guidelinesSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Follow the repository's contribution policy and the user's instructions.
- Distinctive: line 16
Keep the summary concise; use a body for the problem, behavior, or trade-off that the diff cannot explain.
- Distinctive: line 25
Run relevant checks before committing.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Atomic commits
Follow the repository's contribution policy and the user's instructions. Otherwise use Conventional Commits with an imperative, specific summary:
<type>(<optional scope>): <summary>Common types include feat, fix, refactor, docs, test, build, ci, and chore. Keep the summary concise; use a body for the problem, behavior, or trade-off that the diff cannot explain. Mark actual compatibility breaks according to the repository's release convention.
Each commit should contain one coherent concern and leave a usable state. Stage only the intended files or hunks and preserve unrelated user changes. Combine dependent edits when splitting would create a broken intermediate state. Choose reviewable units rather than a target number of commits.
Run relevant checks before committing. Inspect the staged diff for accidental files and sensitive content. Include generated files or configuration only when they are deliberately tracked and required by the repository; exclude temporary artifacts, credentials, and private machine state.
Committing, pushing, and contacting reviewers have separate side effects. Carry out each only within the authorization provided for the task.
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.