Start branch
npx -y skills add dkmqflx/claude-tools --skill start-branchAssembled 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 author says it does
Copied from the file, not written here
Create a new git branch with an appropriate name for the current task and switch to it immediately — no new worktree directory, just a branch. Use when the user wants to start work on a fresh branch from the current position — phrases like "브랜치 만들어줘", "새 브랜치에서 작업 시작", "start a new branch", "create a branch for this", "작업 브랜치 파줘", "/start-branch". Do NOT use when the user explicitly wants a worktree (separate directory).
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, 305 tokens by cl100k_base, as published. Nobody here has run it
Start Branch
Generate an appropriate branch name for the task and switch to it in the current working tree.
When to apply
Starting work on a new feature, fix, or task directly in the current directory. Do not apply for worktree (separate checkout directory) — that is /worktree.
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), ask one short question first. - Create and switch to the branch:
git checkout -b <branch-name> - Confirm in one line:
Switched to new branch: <branch-name> - Begin the user's task.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.