Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.
Install Git Branch Naming
$ npx skills add makeplane/plane --skill branch-name -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install makeplane/plane branch-name --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/makeplane/plane.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/branch-name .claude/skills/branch-name && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "branch-name" agent skill from https://github.com/makeplane/plane/tree/preview/.claude/skills/branch-name into .claude/skills/branch-name/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branch-name", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/makeplane/plane/tree/preview/.claude/skills/branch-nameType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add makeplane/plane --skill branch-name -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install makeplane/plane branch-name --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makeplane/plane.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/branch-name .agents/skills/branch-name && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "branch-name" agent skill from https://github.com/makeplane/plane/tree/preview/.claude/skills/branch-name into .agents/skills/branch-name/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branch-name", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add makeplane/plane --skill branch-name -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install makeplane/plane branch-name --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makeplane/plane.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/branch-name .cursor/skills/branch-name && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "branch-name" agent skill from https://github.com/makeplane/plane/tree/preview/.claude/skills/branch-name into .cursor/skills/branch-name/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branch-name", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/makeplane/plane.git --path .claude/skills/branch-name--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add makeplane/plane --skill branch-name -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install makeplane/plane branch-name --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makeplane/plane.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/branch-name .gemini/skills/branch-name && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "branch-name" agent skill from https://github.com/makeplane/plane/tree/preview/.claude/skills/branch-name into .gemini/skills/branch-name/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branch-name", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install makeplane/plane branch-nameInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add makeplane/plane --skill branch-name -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/makeplane/plane.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/branch-name .github/skills/branch-name && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "branch-name" agent skill from https://github.com/makeplane/plane/tree/preview/.claude/skills/branch-name into .github/skills/branch-name/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branch-name", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add makeplane/plane --skill branch-name -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install makeplane/plane branch-name --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/makeplane/plane.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/branch-name .opencode/skills/branch-name && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "branch-name" agent skill from https://github.com/makeplane/plane/tree/preview/.claude/skills/branch-name into .opencode/skills/branch-name/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branch-name", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
branch-name- GitHub stars
- 60k
- Token cost
- ~594 tokens
- SKILL.md length
- 250 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.
- Works in 5 steps: Determine the type based on the work… → Determine the work item ID → Write the short description → …
- Starting work on a new ticket and needing a branch name
- SKILL.md covers Format, Workflow, Examples and Common Mistakes
- Calls git
What it does
The branch format is a type, a slash, the work item ID and a short description, all lowercase and hyphen-separated, as in `feat/web-1234-app-tile-visibility`. The type is one of feat, fix, chore, refactor, docs or perf, chosen to match the type you would use in the eventual PR title. The work item ID keeps its original form but in lowercase, so SILO-1146 becomes silo-1146. If you do not give one, the agent asks rather than inventing it.
The description is two to five words in kebab-case that name the outcome rather than the implementation, without filler words. The agent then runs `git checkout -b` with the assembled name and returns it. Listed mistakes include putting the ID at the end, using underscores or camelCase, uppercasing the ID, writing a long narrative description and leaving out an ID that exists in Plane. The format is made to work with a companion create-pr skill that reads the ID back out of the branch name.
When your agent uses it
- Starting work on a new ticket and needing a branch name
- Renaming a branch so its work item ID can be extracted
- Picking the right type prefix for a change
Example prompts
- “Create a branch for work item SILO-1146 about relative config URLs.”
- “Rename my branch to match the convention; the ticket is WEB-1234 and it adds app tile visibility.”
- “Name the branch for a docs-only change under WEB-2201.”
Requirements
- A Git repository
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Determine the type based on the work being done
- Determine the work item ID
- Write the short description
- Assemble and create the branch
- Return the branch name to the user.
What it can do on your machine
Read from SKILL.md and the folder at commit 7466675. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Git Branch Naming loads about 594 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 250 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from makeplane/plane at commit 7466675, republished under its AGPL-3.0 licence (© makeplane). 250 words, ~594 tokens.
Download SKILL.mdSave it as
.claude/skills/branch-name/SKILL.md (or your agent's skills folder).- name
- branch-name
- description
- Use when starting a new branch or renaming an existing one — produces a branch name in the format `<type>/<work-item-id>-<short-description>` that's compatible with the create-pr skill's work item ID extraction.
- user_invocable
- true
Branch Naming
Create branch names that follow the convention <type>/<work-item-id>-<short-description>, where the work item ID can be cleanly extracted later (e.g., by the create-pr skill).
Format
<type>/<work-item-id>-<short-description>- All lowercase, hyphen-separated
- Work item ID stays in its original form but lowercased (e.g.,
SILO-1146→silo-1146) - Short description is 2–5 words in kebab-case, focused on the what, not the how
Workflow
Determine the type based on the work being done:
feat— new functionalityfix— bug fixchore— tooling, deps, config, non-user-facing housekeepingrefactor— restructuring without behavior changedocs— documentation onlyperf— performance improvement
Determine the work item ID:
- If the user gives one, use it
- If they reference a Plane work item (e.g., a URL or title), extract the ID
- If none exists, ask the user — don't invent one
Write the short description:
- 2–5 words in kebab-case
- Describe the outcome, not the implementation (
add-app-tile-visibility, notupdate-tile-component) - Skip filler words (
the,a,for)
Assemble and create the branch:
git checkout -b <type>/<work-item-id-lowercased>-<short-description>- Return the branch name to the user.
Examples
fix/silo-1146-relative-config-urls
feat/web-1234-app-tile-visibility
chore/web-2201-bump-eslint
refactor/silo-980-extract-auth-middleware
docs/web-1500-pr-template-update
perf/silo-1310-cache-workspace-lookupCommon Mistakes
- Putting the work item ID at the end instead of after the type (breaks extraction)
- Using underscores or camelCase instead of hyphens
- Uppercasing the work item ID inside the branch name (it should be lowercase here, uppercased only when used as the PR title prefix)
- Writing a long, narrative description — keep it scannable
- Omitting the work item ID when one exists in Plane
- Using a type that won't match the eventual PR type (pick the type you'd use in the PR title)
© makeplane, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/branch-name of makeplane/plane.
Open the folder on GitHubat commit 7466675
Compare with similar skills
Git Branch Naming next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Git Branch Naming this skillmakeplane/plane | 60k | — | ~594 | Automated safety check: Pass | AGPL-3.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Creating Description For Gh PRredis/jedis | 12k | — | ~838 | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT |
Similar skills
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
- Official
Creating Description For Gh PR
redis/jedis
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
More from makeplane/plane
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Create Pull Request with Work Item ID
makeplane/plane
Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.
Plane UI Translation
makeplane/plane
Sets the rules for translating and updating Plane's UI strings across locales: do-not-translate terms, plural forms, placeholders and AI translation review.
Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
Related
Works with
Categories
Questions about Git Branch Naming
What does Git Branch Naming do?
Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name. The branch format is a type, a slash, the work item ID and a short description, all lowercase and hyphen-separated, as in `feat/web-1234-app-tile-visibility`. The type is one of feat, fix, chore, refactor, docs or perf, chosen to match the type you would use in the eventual PR title.
When should I use Git Branch Naming?
Git Branch Naming fits situations like: starting work on a new ticket and needing a branch name; renaming a branch so its work item ID can be extracted; picking the right type prefix for a change.
How do I install Git Branch Naming in Claude Code?
Run `npx skills add makeplane/plane --skill branch-name -a claude-code`. Or copy the skill folder (.claude/skills/branch-name in makeplane/plane) into .claude/skills/branch-name in your project. Claude Code loads it when a task matches its description.
How do I install Git Branch Naming in Codex?
Run `npx skills add makeplane/plane --skill branch-name -a codex`. Or copy the skill folder (.claude/skills/branch-name in makeplane/plane) into .agents/skills/branch-name in your project. Codex loads it when a task matches its description.
Can I use Git Branch Naming in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add makeplane/plane --skill branch-name -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/branch-name, .gemini/skills/branch-name, .github/skills/branch-name and .opencode/skills/branch-name in your project.
What does Git Branch Naming need to run?
Going by SKILL.md and its folder, Git Branch Naming needs the command-line tools its instructions call (git). Our summary lists: A Git repository.
Does Git Branch Naming access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Git Branch Naming safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Git Branch Naming use?
Git Branch Naming is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Git Branch Naming use?
About 594 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Git Branch Naming?
Skills that share tags, products or a category with Git Branch Naming: Finishing a Development Branch (obra/superpowers, 296k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Creating Description For Gh PR (redis/jedis, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Git Branch Naming?
makeplane (a GitHub organization) maintains it in makeplane/plane, which has 60,461 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: makeplane/plane on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.