Start Branch
Create a new git branch with an appropriate name and switch to it — from the current position by default, or from a named base branch (e.g. dev, master, main, stage) when one is specified. Use when the user wants to start work on a fresh branch — phrases like "브랜치 만들어줘", "master에서 브랜치 만들어줘", "dev 기준으로 브랜치 파줘", "stage에서 새 브랜치", "start a new branch", "create a branch for this", "branch off master",…
Install
$ agentstack add skill-dkmqflx-git-workflow-plugin-start-branch ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-dkmqflx-git-workflow-plugin-start-branch) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Start Branch
Generate an appropriate branch name for the task and switch to it — from the current position, or from a named base branch.
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 | 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
- Determine the base:
- If the user named a specific branch (e.g.
dev,master,main,stage), that is the base branch. - Otherwise, the base is the current position — no checkout needed before branching.
- 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.
- If a base branch was named, switch to it and pull latest, then branch from it:
``bash git checkout && git pull git checkout -b ` Otherwise, branch directly from the current position: `bash git checkout -b ``
- Confirm in one line:
Switched to new branch:(append(from )if a base was named) - Begin the user's task.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dkmqflx
- Source: dkmqflx/git-workflow-plugin
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.