# Branch

> Creates git branches with proper naming. Use when creating branches, starting new work, or switching to feature branches.

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

---


# Branch Naming

Use `type/short-description` format.

## Types

- `feat`: User-facing features or behavior changes (must change production code)
- `fix`: Bug fixes (must change production code)
- `docs`: Documentation only
- `style`: Code style/formatting (no logic changes)
- `refactor`: Code restructuring without behavior change
- `test`: Adding or updating tests
- `chore`: CI/CD, tooling, dependency bumps, configs (no production code)

## Examples

```text
feat/cache-policy
fix/robots-txt-503
chore/pre-commit-hooks
docs/update-readme
refactor/simplify-cache-behaviors
```

## Instructions

1. Determine the type based on what the work will accomplish
2. Choose a short, descriptive slug (2-4 words, hyphenated)
3. Create the branch: `git checkout -b type/short-description`