conventional-commits
Skill0 starsChanged 5 months agoMITView on GitHub
Write git commit messages using Conventional Commits v1.0.0. Invoke when committing, staging for commit, amending, rebasing commit messages, or when the user asks for feat:/fix:/docs: format. Do NOT load for unrelated coding tasks.
61 other projects use a version of this.
Adopted by
Most recently taken up by
- imtiazrayhan/agentscamp-librarytheir own version, first seen Nov 16, 2026
- space-code/skillstheir own version, first seen Nov 16, 2026
- pantheon-org/tekhnetheir own version, first seen Nov 15, 2026
- niksavis/basiclytheir own version, first seen Nov 15, 2026
- sauljabin/agentskillstheir own version, first seen Nov 15, 2026
- hanspeterdietiker/open-agent-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use github, grilling and 9 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
GoogleSkillgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Also in 5 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
NVIDIASkillresearch
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
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
- +5 more from google
Other versions61 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 61
- 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
51 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 repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- consult-claudeSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 55 edited versions we read keep these.
5
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 13
Use Conventional Commits v1.0.0 for every git commit you create.
- Distinctive: line 42
No trailing period on the subject line
- Distinctive: line 60
Write subject that states what changed, not how you feel about it
- Distinctive: line 61
Add body only if context helps future readers
- Very specific: line 62
Run git commit -m "type(scope): subject" or heredoc for body
- Distinctive: line 64
When amending or rebasing, rewrite messages to match this format.
“Common” is measured: kept by at least 6 in 10 of the 55 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
Use Conventional Commits v1.0.0 for every git commit you create.
Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]Types
| Type | Use for |
feat | New feature or capability |
fix | Bug fix |
docs | Documentation only |
style | Formatting, no logic change |
refactor | Restructure without feat/fix |
perf | Performance improvement |
test | Tests |
chore | Build, deps, tooling |
ci | CI/CD changes |
Rules
- Imperative mood:
add handlernotadded handler - No trailing period on the subject line
- Subject ≤ 72 characters
- Scope when helpful:
fix(consult):,feat(auth): - Breaking changes: footer
BREAKING CHANGE: <description>
Examples
feat: add consult-claude skill
fix(consult): block Bash via allow-list tools
docs: add install instructions to README
chore: bump dependencyWorkflow
- Review staged changes (
git diff --cachedorgit status) - Pick type and optional scope from the diff
- Write subject that states what changed, not how you feel about it
- Add body only if context helps future readers
- Run
git commit -m "type(scope): subject"or heredoc for body
When amending or rebasing, rewrite messages to match this format.
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.

