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.
npx skills add github/awesome-copilot --skill conventional-branch --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Conventional Branch Create Git branches that follow the [Conventional Branch](https://conventional-branch.github.io) specification — a simple, consistent convention for naming Git branches. ## Branch Name Format ``` <type>/<description> ``` ### 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 descr
- Branch Name Format
- Branch Types
- Trunk Branches
- Naming Rules
- Valid Examples
- Invalid Examples
- Description Guidelines
- Workflow
- Relationship with Conventional Commits
Prefer the remote's default branch git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||' for b in develop main master; do git show-ref --verify --quiet "refs/heads/$b" && echo "$b" && break done git checkout <base> git pull origin <base> git checkout -b <type>/<description>
What does the conventional-branch skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill conventional-branch --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.