---
description: Git Branch Naming Rules
globs:
alwaysApply: true
---

## Branch naming

- Use lowercase branch names.
- Use a type prefix and a short description in kebab-case.
- Format: `<type>/<short-description>` or `<type>/<issue-id>-<short-description>`
- Use `gh-123` as the issue id format (avoid `#` in branch names).

### Allowed types

- `feat` - new features
- `fix` - bug fixes
- `docs` - documentation changes
- `chore` - maintenance / tooling
- `refactor` - code refactoring (no behavior change)
- `test` - tests only
- `build` - build system changes
- `ci` - CI changes
- `perf` - performance improvements
- `style` - formatting / lint-only changes
- `revert` - reverting prior changes

### Examples

- `feat/gh-123-add-stepper-component`
- `fix/markdown-table-overflow`
- `docs/gh-45-update-contributing`
- `chore/update-pnpm-lock`

### Notes

- Branch off `dev` by default (unless maintainers request otherwise).
- Avoid spaces, uppercase letters, and special characters other than `/` and `-`.