dkmqflx Start Branch from Dev
Pull the latest dev, then create a well-named branch for the task.
When to apply
Starting work that must be based on the latest dev. Do not apply when branching off the current position is fine — that is /start-branch.
Branch naming convention
Format: <type>/<short-description>
| Type | When to use |
|---|---|
feat/ |
New feature or capability |
fix/ |
Bug fix |
chore/ |
Maintenance, config, dependency updates |
refactor/ |
Restructuring without behavior change |
docs/ |
Documentation only |
test/ |
Test additions or changes |
Description rules: lowercase, hyphen-separated, 2–5 words, describes WHAT (not HOW).
Examples: feat/user-authentication, fix/cart-total-calculation, chore/update-eslint-config, refactor/extract-payment-service
Steps
- Derive the branch name from the user's task description using the convention above.
If no task description was given (bare
/start-branch-from-dev), ask one short question first. - Switch to dev and pull latest:
git checkout dev && git pull - Create and switch to the new branch:
git checkout -b <branch-name> - Confirm in one line:
Branched off latest dev → now on <branch-name> - Begin the user's task.