conventional-commits
Skill62 starsChanged 3 days agoMITView on GitHub
Use before writing a commit message, PR title, PR description or branch name, or adding or removing a label in langchain-litellm. Covers the Conventional Commits title rules that pr-title-lint.yml checks, the PR description rules that keep release-please from dropping or duplicating a commit, branch names, dependency commits that must ship in a release, and which labels bots own.
62 other projects use a version of this.
Adopted by
Most recently taken up by
- lyeyixian/skillstheir own version, first seen Nov 16, 2026
- 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
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 versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- 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
- WncFht/agent-basic-skill★ 30same name
- hankunpeng/skills★ 26same name
- metalagman/agent-skills★ 24same name
- jackjin1997/ClawForge★ 12same name
- pantheon-org/tekhne★ 10same name
52 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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 12
Every commit message and every PR title follows Conventional Commits 1.0.0: <type>[(<scope>)][!]: <description>.
- Very specific: line 23
No line starts with a word joined to (, such as foo( or
foo(, unless that ( closes before any other ( - Very specific: line 25
No paragraph starts with <type>: or <type>(<scope>):, which release-please reads as a second commit.
- Very specific: line 33
Never push to main. Every change goes through a PR, and the main-protection ruleset blocks direct pushes for everyone.
“Common” is measured: kept by at least 6 in 10 of the 56 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 for langchain-litellm
main takes squash merges only. The squash commit's subject is the PR title and its body is the PR description; branch commits never reach main. release-please computes the version and changelog from those squash commits, and label-pr.yml labels the PR from its title. A malformed title means a wrong release, a missing changelog entry and a wrong label.
Titles and commit messages
- Every commit message and every PR title follows Conventional Commits 1.0.0:
<type>[(<scope>)][!]: <description>.- The type is lowercase.
- The scope is optional, names one subsystem such as
chat_models,router,depsorrelease, and is never an empty(). - The description is imperative, starts with a lowercase verb, keeps identifiers and proper nouns in their own case, and has no trailing period.
- CI checks the type, the header shape and the empty scope. The rest is on the author.
- The type is one of the
types:in.github/workflows/pr-title-lint.yml, which is the source of truth: check it. Today: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert. - A breaking change puts
!before the colon, and only a breaking change carries it.label-pr.ymldetects only!, so aBREAKING CHANGE:footer alone gets nobreakinglabel.
PR descriptions
- The PR description must parse as a commit body. It becomes the squash commit body, whoever merges can rewrap it, and release-please tries every body line as a footer.
- No line starts with a word joined to
(, such asfoo(or`foo(, unless that(closes before any other(and before the line ends. Code blocks count, and indenting their lines does not help: the squash rewraps the description at about 72 columns and drops the indent. - So a call with a space or a nested paren inside, such as
foo(a, b), stays out of the description, code blocks included, or the PR gets aBEGIN_COMMIT_OVERRIDEblock before the merge. A call likefoo(x)is safe anywhere. - No paragraph starts with
<type>:or<type>(<scope>):, which release-please reads as a second commit. Do not repeat the title as a line of the description. - Close an open issue with
Fixes #N. Link an issue that is already closed withFollow-up to #N, neverFixesorRefs, because release-please prints every footer reference as "closes #N". - release-please drops a commit it cannot parse, and the release-please job still succeeds. The
release-notesjob then fails on the push tomain. The fix is aBEGIN_COMMIT_OVERRIDEblock in the PR description, added before the merge when the description is at risk, or afterwards followed by a re-run of Release.
- No line starts with a word joined to
Dependencies and branches
- A dependency change that users need released uses
fix(deps).buildhas no entry inchangelog-sectionsinrelease-please-config.json, so it cuts no release. - Branch names are
<type>/<kebab-case-slug>with the same type as the PR title, for exampleci/label-dependabot-security-prs. Bot branches are exempt. - Never push to
main. Every change goes through a PR, and themain-protectionruleset blocks direct pushes for everyone.
Labels
- Respect label ownership.
- PR type labels
feat,fix,docs,refactor,chore,ci,test,perf,buildandbreaking:label-pr.ymlapplies them from the title when a PR is opened or edited, and removes any the title no longer implies. Never set them by hand on PRs.styleandreverthave no label. - Bot-owned:
autorelease: pendingandautorelease: tagged(release-please);dependencies,python,python:uvandgithub_actions(Dependabot). Never add or remove them. - Issue labels: the issue templates apply
bug,feature requestortask. Everything else is manual triage by a maintainer:duplicate,invalid,wontfix,question,good first issue,help wanted,upstream,security,regression, and type labels such asdocs,choreorcion issues. bugandfeature requestare for issues,fixandfeatfor PRs. Never swap them.
- PR type labels
Actions
- Pin any new or updated GitHub Action to a full commit SHA with a comment naming its full release, such as
# v6.1.1, as every existinguses:line is. A pre-commit hook rejects a shorter comment such as# v6.
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.

