Create Feature Branch
release/* ブランチから作業ブランチを作成する(branch-management 規約に準拠)。
Branch Naming Convention
| Prefix | Purpose | Example |
|---|---|---|
feat/ |
New feature | feat/issue-88-return-mode |
fix/ |
Bug fix | fix/stdout-encoding |
refactor/ |
Refactoring | refactor/output-processor |
update/ |
Dependency updates | update/jsr-packages |
remove/ |
Feature removal | remove/deprecated-api |
docs/ |
Documentation | docs/update-readme |
Workflow
1. Ensure clean working directory
git status
If there are uncommitted changes, ask user how to handle them.
2. Find active release branch
git branch -a | grep 'release/'
If no release branch exists, create one from develop first (see /release-procedure).
3. Update release branch
git checkout release/vX.Y.Z
git pull origin release/vX.Y.Z
4. Create work branch from release
git checkout -b feat/issue-{NUMBER}-{DESCRIPTION}
5. Confirm creation
git branch --show-current
Checklist
- Working directory is clean
- Active release branch identified
- Release branch is up to date
- Branch name follows convention
- Branch is created from release/* (NOT from develop or main)
Notes
- Always branch from
release/*, notdevelopormain(branch-management 規約) - Include issue number in branch name for traceability
- Use lowercase with hyphens for descriptions
- If no release branch exists, ask user to create one first
Converted and distributed by TomeVault — claim your Tome and manage your conversions.