Start branch from dev
Skill dkmqflx/claude-tools/.claude/skills/start-branch-from-dev
Sync the local dev branch to the latest remote, then create a new well-named branch from it and switch to it. Use when the user wants to start fresh work based on dev — phrases like "dev에서 브랜치 만들어줘", "dev 기준으로 작업 시작", "dev 기반 브랜치", "start from dev", "branch off dev", "/start-branch-from-dev". Do NOT use when branching from the current position is fine — use /start-branch for that.From its SKILL.md
npx -y skills add dkmqflx/claude-tools --skill start-branch-from-devAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, 330 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.