conventional-commits
Skill1 starsChanged 5 days agoMITView on GitHub
Generate clear Conventional Commits messages from staged changes. Use when committing code and you want a well-structured, consistent commit message.
61 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- 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
- hankunpeng/skillstheir own version, first seen Nov 10, 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 · 1
- minagayid/Agents★ 111% same
Wrote their own version · 60
- 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
50 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 repository163 other files it gives its agents.
- agents.mdAGENTS.md
- 3d-asset-handoff-sheetSkill
- accessibility-regression-auditorSkill
- adr-writerSkill
- agent-memory-designerSkill
- agent-trajectory-evaluatorSkill
- alerting-rules-tunerSkill
- analysis-memo-writerSkill
- annotation-disagreement-ledgerSkill
- annotation-task-spec-builderSkill
- api-deprecation-plannerSkill
- api-error-contract-designerSkill
- architecture-diagram-generatorSkill
- asset-metadata-review-ledgerSkill
- auth-flow-reviewerSkill
- background-job-reliability-auditorSkill
- branch-rebaserSkill
- brand-voice-profilerSkill
- bundle-analyzerSkill
- cache-policy-designerSkill
- canary-release-plannerSkill
- caption-correction-ledgerSkill
- changelog-from-prsSkill
- chart-chooserSkill
- chunking-strategy-optimizerSkill
- circular-dependency-breakerSkill
- claude-settings-auditorSkill
- code-example-verifierSkill
- cold-email-deliverability-auditorSkill
- cold-start-optimizerSkill
- commit-splitterSkill
- competitor-teardownSkill
- component-spec-writerSkill
- connection-pool-tunerSkill
- content-repurposerSkill
- contract-obligation-registerSkill
- contract-test-designerSkill
- cors-configuratorSkill
- coverage-gap-finderSkill
- crm-export-auditorSkill
- dashboard-designerSkill
- data-retention-auditorSkill
- dataset-first-lookSkill
- dead-code-finderSkill
- deadlock-diagnoserSkill
- decision-log-reconcilerSkill
- dependency-auditSkill
- dependency-upgrade-plannerSkill
- design-brief-writerSkill
- design-critique-checklistSkill
- design-token-extractorSkill
- devcontainer-designerSkill
- distributed-tracing-instrumenterSkill
- dockerfile-optimizerSkill
- email-sequence-drafterSkill
- embedding-index-tunerSkill
- embedding-set-inspectorSkill
- entity-match-candidate-ledgerSkill
- exit-ticket-builderSkill
- extract-moduleSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Read the staged diff to understand what actually changed:
- Distinctive: line 26
If nothing is returned, stop and tell the user there are no staged changes to commit.
- Distinctive: line 27
Check the staged file list for scope hints (directory or package names):
- Very specific: line 42
Write the subject line: type(scope): summary
- Distinctive: line 44
No trailing period; aim for 50 characters, hard limit 72.
- Distinctive: line 45
If the change is non-trivial, add a blank line then a body explaining the motivation and any context the diff alone does not convey.
- Very specific: line 46
If the change breaks compatibility, mark it: append !
- Very specific: line 47
Add footers for issue references when relevant (e.g.
“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
This skill inspects your staged changes and produces a commit message that follows the Conventional Commits specification. It picks the right type and scope, writes a concise imperative subject, adds a body explaining the why when the change is non-trivial, and flags breaking changes correctly — so your history stays readable and your tooling (changelogs, semantic-release) keeps working.
When to use this skill
- You have changes staged with
git addand want to commit them. - You want a consistent, spec-compliant message instead of free-form text.
- You are unsure which type (
feat,fix,chore, …) fits the change. - Your repo uses semantic versioning or automated changelog generation that depends on commit conventions.
[!NOTE] This skill only reads and commits what is already staged. Stage the exact hunks you want first (
git add -p). It will not stage files for you.
Instructions
- Read the staged diff to understand what actually changed:
If nothing is returned, stop and tell the user there are no staged changes to commit.git diff --cached - Check the staged file list for scope hints (directory or package names):
git diff --cached --name-only - Choose the type from the staged changes:
feat— a new user-facing capabilityfix— a bug fixdocs— documentation onlystyle— formatting, no logic changerefactor— code change that neither fixes a bug nor adds a featureperf— performance improvementtest— adding or correcting testsbuild/ci— build system or pipeline changeschore— maintenance, deps, tooling
- Derive an optional scope in parentheses from the affected area (e.g.
auth,api,parser). Omit it if the change is broad. - Write the subject line:
type(scope): summary- Imperative mood ("add", not "added" or "adds").
- No trailing period; aim for 50 characters, hard limit 72.
- If the change is non-trivial, add a blank line then a body explaining the motivation and any context the diff alone does not convey. Wrap at ~72 columns.
- If the change breaks compatibility, mark it: append
!after the type/scope (e.g.feat(api)!:) and add aBREAKING CHANGE:footer describing the migration. - Add footers for issue references when relevant (e.g.
Refs: #123,Closes: #456). - Present the proposed message to the user for confirmation, then commit:
git commit -m "feat(parser): add support for nested arrays" \ -m "Handles arbitrarily deep nesting by recursing on bracket pairs." \ -m "Closes: #128"
Examples
Suppose git diff --cached --name-only shows src/auth/session.ts and the diff replaces a 1-hour token TTL with a configurable value, removing the old constant.
feat(auth)!: make session token TTL configurable
Replace the hardcoded 1-hour TTL with SESSION_TTL_SECONDS so deployments
can tune session lifetime without a rebuild. Falls back to 3600 when the
variable is unset.
BREAKING CHANGE: the SESSION_MAX_AGE constant has been removed. Set the
SESSION_TTL_SECONDS environment variable instead.
Closes: #214Commit it:
git commit \
-m "feat(auth)!: make session token TTL configurable" \
-m "Replace the hardcoded 1-hour TTL with SESSION_TTL_SECONDS so deployments can tune session lifetime without a rebuild. Falls back to 3600 when the variable is unset." \
-m "BREAKING CHANGE: the SESSION_MAX_AGE constant has been removed. Set the SESSION_TTL_SECONDS environment variable instead." \
-m "Closes: #214"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.

