git-best-practices
Skill1 starsChanged 6 months agoMITView on GitHub
Git best practices for commit messages and branch workflow. Use when writing or reviewing commit messages, advising on branching, merging, rebasing, PRs, or keeping a clean linear history.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kayaman/skillstheir own version, first seen Mar 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kayaman/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 repository7 other files it gives its agents.
- braid-promptingSkill
- lucide-iconsSkill
- memgooseSkill
- milkdownSkill
- raison-sdkSkill
- readme-creatorSkill
- reka-uiSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 14
Read the relevant reference file(s) before advising.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Git Best Practices
Three core areas:
- Commit messages — how to write clear, meaningful commit messages
- Branch workflow — how to keep a clean, linear history using rebase
- Branch naming — how to name branches clearly without noisy prefixes
Read the relevant reference file(s) before advising.
References
- references/commit-messages.md — The 7 rules for great commit messages. Read when writing, reviewing, or advising on commit messages.
- references/git-workflow.md — Rebase-first branch workflow for clean history. Read when advising on branching strategy, PRs, merging, or conflict resolution.
- references/branch-naming.md — Flat, descriptive branch naming guidance. Read when creating or reviewing branch names.
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.