conventional-commits
Skill3 starsChanged 22 days agoMITView on GitHub
Use for ALL commits — enforces incremental commits with Conventional Commits prefixes and descriptive messages in the project language.
56 other projects use a version of this.
Adopted by
Most recently taken up by
- langchain-ai/langchain-litellmtheir own version, first seen Nov 8, 2026
- r3b1s/skillstheir own version, first seen Nov 8, 2026
- niksavis/handilytheir own version, first seen Nov 8, 2026
- sambulosenda/Skillstheir own version, first seen Nov 8, 2026
- niksavis/basiclytheir own version, first seen Nov 7, 2026
- Gu-ZT/skillstheir own version, first seen Nov 4, 2026
Used with
Projects with it also use github, domain-modeling and 8 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.
NVIDIASkillgithub
Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.
Also in 3 projects that use this
GoogleSkilldomain-modeling
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Also in 4 projects that use this
- NVIDIASkill
research
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 5 projects that use this
- GoogleSkill
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 5 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
- +4 more from google
Other versions56 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 56
- open-sdr/openwifi★ 4.9ksame name
- endurain-project/endurain★ 2.4ksame name
- joaovitoriasilva/endurain★ 2.4ksame name
- awattar/claude-code-best-practices★ 250same name
- dgalarza/agent-skills★ 72same name
- langchain-ai/langchain-litellm★ 62same name
- WncFht/agent-basic-skill★ 30same name
- hankunpeng/skills★ 26same name
- metalagman/agent-skills★ 24same name
- jackjin1997/ClawForge★ 12same name
46 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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectural-decision-recordsSkill
- gherkin-specsSkill
- git-workflowSkill
- grillingSkill
- implementation-standardsSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-workflowSkill
- session-endSkill
- session-startupSkill
- test-driven-developmentSkill
- update-harnessSkill
- using-git-worktreesSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
4
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 16
Always: Every commit follows this convention, from the first change to the end of the session.
- Very specific: line 20
Write the message in the project language (language.user).
- Distinctive: line 25
Commit immediately after completing ONE atomic change:
- Distinctive: line 52
Do not wait until the end of the session to commit.
- Distinctive: line 65
Only when the commit is executed by an agent.
“Common” is measured: kept by at least 6 in 10 of the 51 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
Conventional Commits
Overview
Make small, incremental commits after each completed logical change. Use standardized prefixes to make the history navigable and allow selective reverts.
When to Use
Always. Every commit follows this convention, from the first change to the end of the session.
Language
Write the message in the project language (language.user). The examples below use English for
readability: translate the message, never the prefix.
Golden rule: one logical change = one commit
Commit immediately after completing ONE atomic change:
- ✅ Spec written →
docs: spec for <entity> registration - ✅ Test implemented →
test: reject duplicate identifier - ✅ Code implemented →
feat: register <entity> - ✅ ADR created →
docs: ADR 0001 - persistence decisions - ✅ Refactor →
refactor: extract identifier validation into a method - ❌ Do NOT accumulate: "add spec, test, code, ADR and fix bug" in a single commit
Prefixes
| Prefix | When to use | Example |
feat: | New domain feature (code) | feat: register <event> with multiple items |
test: | New or modified tests | test: reject transition from invalid state |
docs: | Specs, ADRs, documentation (no code) | docs: spec for lifecycle states |
refactor: | Structural change without functional change | refactor: extract state machine into a private method |
fix: | Bug fix | fix: validate null identifier before comparing |
chore: | Config, build, project files | chore: update linter configuration |
Workflow
- Make one atomic change
git add <files>git commit -m "<prefix>: <descriptive message>"- Repeat
Do not wait until the end of the session to commit. Incremental commits allow reverting specific changes without affecting the rest.
Role byline (when the commit is executed by an agent)
Commits executed by an agent carry the role as a byline at the end of the body:
git commit -m "feat: register <event> with multiple items
By <role>."- Only when the commit is executed by an agent. User commits do not carry a byline.
- The byline goes in the body, never in the title (the title keeps the conventional prefix).
- Examples:
By analyst.,By engineer.,By qa-analyst.
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.