create-branch
/create-branch
Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically.
- Author
- tartinerlabs ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically.
Original author description
Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically.
How it works
- Rules Overview
- Workflow
SKILL.md preview
--- name: create-branch description: Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically. license: MIT allowed-tools: Read Bash(git:*) Bash(gh:*) Bash(glab:*) model: haiku effort: low compatibility: Requires git; issue-linking uses a GitHub (gh) or GitLab (glab) remote metadata: short-description: Validated branch names linked to issues. --- You create and checkout git branches with validation. ## Rules Overview | Rule | Impact | File | |------|--------|------| | Branch naming | HIGH | `rules/branch-naming.md` | | Prefix detection | MEDIUM | `rules/prefix-detection.md` | ## Workflow 1. If an issue number is provided, detect the remote host from `git remote get-url origin` (github.com → gh, gitlab.com → glab; default GitHub). On **GitHub**, use `gh issue develop <number> -c` to create a linked branch and skip to step 4. On **GitLab** (no direct equivalent), include the issue number in the branch name (e.g. `feature/123-description`) so the MR auto-links, then continue through steps 2–4 2. Auto-detect prefix from user input (see `rules/prefix-detection.md`), validate name (see `rules/branch-naming.md`), and check for duplicates locally and remotely 3. Create and checkout from `main` → `master` → current HEAD: `git checkout -b <name> <base>`. **Exception**: when the current branch has an open unmerged PR and the new work builds on it (the user says "on top of this" / "next part", or the change depends on unmerged work), base on the current branch instead — the diff stays scoped to the new layer, and on GitHub the resulting PRs link into a stack automatically 4. Offer remote push: `git push -u origin <name>`
Files in this package (3)
- SKILL.md 2 KB
- rules/branch-naming.md 1 KB
- rules/prefix-detection.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · tartinerlabs/skills | 90 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| sickn33/agentic-awesome-skills | 100 | MIT |
| getsentry/skills | 100 | Apache-2.0 |
| tmj-90/gaffer | 100 | Apache-2.0 |
| pinkpixel-dev/skills-collection-1 | 100 | Apache-2.0 |
| zte-aicloud/co-omnispec | 100 | MIT |
| OutlineDriven/outline-driven-development | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 8e213d04d465 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100git-branch-create
Create a new git branch using a conventional naming scheme. Use when the user asks to create a branch, start a new branch, /git-branch-create, or signals they are beginning a discrete piece of work - "start work on X", "spin up a branch for Y", "let's start Z". Boundary: a… - 100branch
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes. - 100start
Begins a new piece of work in the ai-agent-skills repository. Two modes: EXISTING ISSUE (user provides a GitHub issue number or URL — fetches it, cuts the correct branch) and NEW ISSUE (user describes what needs doing — classifies as feature or bug, drafts a structured… - 100branch
Creates new git branch with corresponding spec directory structure. Triggers on keywords: create branch, new branch, branch with spec - 100creating-issues-and-pull-requests
Use when creating GitHub pull requests or issues with template compliance. Triggers: 'create a PR', 'open a pull request', 'file an issue', 'create issue'. Also invoked by finishing-a-development-branch. NOT for: deciding whether to merge or PR (use finishing-a-development-branch). - 86branch
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.