branch-strategy
Installation
SKILL.md
Branch Strategy
Branch Naming Conventions
Every branch name must follow a structured prefix convention. This keeps the repository navigable, enables CI/CD automation, and makes intent immediately clear.
Required Prefixes
| Prefix | Purpose | Example |
|---|---|---|
feature/ |
New functionality or capability | feature/user-avatar-upload |
fix/ |
Bug fixes for existing behavior | fix/login-redirect-loop |
hotfix/ |
Urgent production fixes | hotfix/payment-null-pointer |
release/ |
Release preparation and stabilization | release/2.4.0 |
chore/ |
Maintenance, dependencies, tooling | chore/upgrade-eslint-9 |
docs/ |
Documentation-only changes | docs/api-authentication-guide |
refactor/ |
Code restructuring without behavior change | refactor/extract-billing-service |
test/ |
Adding or fixing tests only | test/payment-edge-cases |
experiment/ |
Exploratory work, not intended for merge | experiment/graphql-federation |