Agent skill · software engineering · github
conventional-branch
Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Use when creating a new branch, naming a branch, or checking whether a branch name complies with the spec.
Why this skill is useful
Codifies a specific naming convention for Git branches that the AI could infer but now doesn't have to guess.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Conventional Branch Create Git branches that follow the Conventional Branch specification — a simple, consistent convention for naming Git branches. Branch Name Format Branch Types Type Alias Purpose ------ ------- --------- feature/ feat/ New features or enhancements bugfix/ fix/ Bug fixes hotfix/ — Urgent production fixes release/ — Release preparation (dots allowed in version: release/v1.2.0) chore/ — Non-code tasks (deps, docs, config) Trunk Branches main, master, and develop are trunk branches — they do not use a prefix. Never create new branches with the same names as trunk branches; branch off them instead. Naming Rules Lowercase only — no uppercase letters anywhere Alphanumerics, hyphens, and dots — a-z, 0-9, -, . Dots allowed only in release/ version descriptions (e.g., release/v1.2.0) No underscores, spaces, or special characters No consecutive hyphens (--), dots (..), or hyphen-dot adjacency (-. or .-) No leading or trailing hyphens or dots in the description Valid Examples Invalid Examples Branch Problem -------- --------- Feature/Add-Login Uppercase letters feature/new--login Consecutive hyphens feature/-new-login Leading hyphen feature/new-login- Trailing hyphen release/v1.-2.0 Hyphen adjacent to dot fix/header bug Space fix/headerbug Underscore unknown/some-task Unknown prefix type Description Guidelines Use kebab-case with 2-5 words Be descriptive but concise (~50 chars total) Good: add-oauth-login, fix-header-overflow, update-ci-config Bad: fix-bug, new-feature Workflow Follow these steps: Step 1 — Determine Branch Type Ask the user (if not already clear): Branch type — default to feature when uncertain Brief description — what the branch is for If the user mentions a ticket or issue number, include it in the description (e.g., feature/issue-123-add-oauth). Step 2 — Validate the Name Check the assembled name against the Naming Rules above. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/conventional-branch