# Create Branch

> Git branch naming guidelines. Use when creating, renaming, or checking out new branches.

- Skill: `majiayu000/create-branch-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/create-branch-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/create-branch-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/create-branch-2

---


# Git Branch Naming Guidelines

Follow the Conventional Branch specification with these details:

## Prefixes

Except for `main`, all branch names must use one of:

- `feat/`: New features (e.g., `feat/add-login-page`)
- `fix/`: Bug fixes (e.g., `fix/header-bug`)
- `hotfix/`: Urgent fixes (e.g., `hotfix/security-patch`)
- `release/`: Release preparation (e.g., `release/v1.2.0`)
- `chore/`: Non-code tasks (e.g., `chore/update-dependencies`)

## Additional Rules

- Include ticket numbers when applicable (e.g., `feat/issue-123-new-login`)
- Dots allowed only for version numbers in `release/` branches
- Check existing branches for naming patterns before creating new ones
- Do NOT use `git -C <path>` when the current directory is already the repository root