branch-strategy
Installation
SKILL.md
Branch Strategy
Use this skill when
- Setting protected branches and rules
- Naming conventions for branches
- Managing release and hotfix branches
Do not use this skill when
- Individual commit hygiene (use commit-quality)
- Git mechanics
Instructions
- Protect main: require reviews, green checks, no direct pushes.
- Name branches by purpose: feature/xxx, fix/xxx, release/xx.
- Keep releases traceable: tags and release branches defined.
- Set CI on every PR branch.
- Define merge rules: squash for feature, merge for release.
- Clean up merged branches regularly.