# Branch Name

> When naming Git branches, provide guidelines on the recommended branch naming conventions for the project.

- Skill: `majiayu000/branch-name` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/branch-name`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/branch-name/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/branch-name

---


## Basic Policy

- Prioritize branch names that clearly indicate their purpose at a glance
- Use a structure of prefix + `/` + identifier
- Use lowercase and kebab-case for the identifier
- Do not use characters other than alphanumeric and allowed symbols

## Prefix List

- `feat`: Add new features
- `fix`: Fix bugs in existing features
- `hotfix`: Urgent fixes that need immediate deployment
- `refactor`: Refactoring without changing functionality
- `chore`: Non-functional tasks such as dependency updates and CI configuration adjustments
- `docs`: Adding or modifying documentation (not related to functionality)
- `test`: Adding or modifying test code (not related to functionality)
- `release`: Release preparation tasks

## Identifier Naming Rules

- Keep branch names short and meaningful
- Connect words using kebab-case
- Include the issue number at the beginning if the branch is based on an issue
- Write identifiers in English