Create branch

Skill tartinerlabs/skills/skills/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.From its SKILL.md

Install

npx -y skills add tartinerlabs/skills --skill create-branch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 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.7 KB, as published. Nobody here has run it

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

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
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
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
Offer remote push: git push -u origin <name>

What ships with it: 2 files

1.5 KB alongside SKILL.md

rules/

branch-naming.md598 B
prefix-detection.md900 B

Gives 0 of the 12 instructions most pr commit review skills give

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Use gh issue develop for GitHub issues
Include issue number in GitLab branch names
Auto-detect prefix from user input
Validate branch name against naming rules
Check for duplicate branch names
Base on current branch if work is stacked

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.