About

The Conventional Branch specification was inspired by Conventional Commits.

AI Agent Source Prefixes

As AI coding agents increasingly open their own pull requests, Conventional Branch maintains a registry of their branch prefixes so tools and teams can recognize them consistently. This registry is the machine-readable source of truth — the table below is generated from data/agents.yaml.

Giving each agent a documented prefix (or using the vendor-neutral ai/) lets teams do more than just eyeball who opened a PR:

• Apply review policy by source — require an extra human approval on agent-generated branches, or auto-assign a reviewer to them.
• Route CI differently — run a heavier security, license, or lint suite on ai/, copilot/, claude/, … branches before they reach a human reviewer.
• Attribute activity and cost — measure how much work each agent produces by filtering branches and PRs on their prefix.
• Automate housekeeping — auto-label PRs, apply branch-protection rules, or trigger notifications based on the prefix.

Building an agent that opens PRs? Register its prefix so reviewers and tooling recognize it out of the box.

Tooling for Conventional Branch

Conventional Branch can be adopted with local checks, CI validation, editor support, and agent skills:

• commit-check: Commit Check supports checking commit messages, branch naming, committer name/email, commit signoff, customizing error messages, suggested commands and more.
• commit-check-action: A GitHub Action for checking commit message formatting, branch naming, committer name, email, commit signoff and more.
• VSCode Conventional Branch: Customizable Conventional Branch support for Visual Studio Code.
• Conventional Branch Skill: Agent skill for AI coding assistants.

Install the skill with:

npx skills add conventional-branch/conventional-branch --skill conventional-branch

Projects Using Conventional Branch

• BerriAI/litellm: A high-performance LLM proxy supporting 100+ models with spending tracking and guardrails.
• karol-broda/snitch: A prettier way to inspect network connections.
• ansible/metrics-utility: Standalone utility for github.com/ansible/awx.
• sanity-io/sdk: Sanity App SDK.
• TexasInstruments/processor-sdk-doc: Texas Instruments Processor SDK documentation.
• dunossauro/fastapi-do-zero: Curso básico de FastAPI em português.
• Enedis-OSS/tic4eebus: EEBUS OPEV use case by Enedis, France’s largest electricity distributor.
• bcgov/nr-pies: Natural Resource Permitting Information Exchange by the Government of British Columbia.
• commit-check: A free, powerful tool that enforces commit metadata, branch naming, and more.
• ZeusAutomacao/DFe.NET: Biblioteca em C# para emissão e impressão de NFe, NFCe, MDF-e e CT-e.
• RLinf/RLinf: Reinforcement Learning Infrastructure for Agentic AI.
• Curiosum: Building apps for innovators.
• jal-co/shieldcn: Beautiful README badges inspired by shadcn/ui.
• LedgerHQ/ledger-live: Mono-repository for packages related to Ledger Live and its JavaScript ecosystem.
• … and more projects using Conventional Branch.

Want your project on this list? Send a pull request.

How to Adopt

1. Communicate the convention to your team and add it to your contributing guidelines.
2. Enforce it automatically using one of the tools listed above.
3. Add the badge to your repository README to signal adoption.
4. Configure your CI/CD to trigger different workflows based on branch prefix (e.g., auto-deploy on release/ branches).