conventional-branch
Installation
SKILL.md
Conventional Branch
Create branch names that are easy to scan, easy to sort, and easy to align with Conventional Commits.
When to Use
- Starting a new task and no branch exists yet
- Renaming or validating a branch before pushing it
- Aligning branch naming with a team convention such as
feature/...orfix/... - Mapping a work item to a predictable branch slug before parallel work begins
When NOT to Use
| Instead of conventional-branch | Use |
|---|---|
| Writing or splitting commit messages | commit-workflow |
| Creating isolated parallel checkouts for multiple branches | using-git-worktrees |
| Switching to an already agreed branch name with no validation needed | create or checkout the branch directly |