| name | new-branch |
| description | Creates a new git branch following the project's branch naming convention. Use this skill whenever the user wants to start new work, create a branch, switch to a new branch. |
Create a new git branch and switch to it, following the project branch naming convention.
Steps:
- If the purpose of the branch is unclear, ask the user before proceeding
- Check for uncommitted changes with
git status --porcelain -uno
- If output is non-empty, stop immediately and print:
"uncommitted changes가 있습니다. 커밋하거나 stash 후 다시 실행하세요."
- Switch to develop and pull the latest changes:
git checkout develop
git pull --rebase origin develop
- Determine the appropriate type and write a concise kebab-case description in English
- Run
git checkout -b type/description
- Confirm with
git branch --show-current
Branch name format: type/description
Types:
- feat: new feature
- fix: bug fix
- style: code formatting (no logic change)
- refactor: code refactoring
- comment: add or update comments
- docs: documentation update
- test: test related changes
- chore: build or package manager config (e.g. Gradle)
- rename: rename or move files/folders
- remove: delete files/folders
Rules:
- Use kebab-case for the description
- Keep the description short and descriptive
- Write the description in English
Example: feat/user-jpa-entity
