branch
Skill1 starsChanged 11 days agoMITView on GitHub
Start work on a new branch or worktree. Use when asked to start a new branch, new worktree, begin work on a feature/fix, or start fresh. Supports issue numbers and plain descriptions.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- isksss/skillstheir own version, first seen Nov 15, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- laz3rjenkins/atomic-commitstheir own version, first seen Nov 8, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- islandhopper81/claude-skillstheir own version, first seen Nov 1, 2026
- JPInert/claude-code-skillstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use handoff.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- egregore-labs/egregore★ 293same name
- ahonn/dotfiles★ 62same name
- Integralist/agent-skills★ 29same name
- iamneilroberts/claude-skills★ 26same name
- Mindgames/skills★ 4same name
- bang9/claude-code-settings★ 2same name
- stijnvanhulle/agents★ 2same name
- isksss/skills★ 1same name
- c0d3ster/claude-skills★ 0same name
- islandhopper81/claude-skills★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-codeSkill
- analyze-projectSkill
- analyze-testsSkill
- audit-mergesSkill
- babysit-prSkill
- backlogSkill
- coderabbitSkill
- commitSkill
- greptileSkill
- implement-issuesSkill
- issueSkill
- jiraSkill
- lintro-addSkill
- lintro-reviewSkill
- lintro-verifySkill
- lintSkill
- properizeSkill
- pr-raycastSkill
- prSkill
- raycastSkill
- rebaseSkill
- reconcileSkill
- scorecardSkill
- stand-ciSkill
- stand-generalSkill
- stand-odinSkill
- stand-pySkill
- stand-rustSkill
- stand-tsSkill
- sweep-prsSkill
- test-apiSkill
- test-shellSkill
- testSkill
- test-ui-qsfSkill
- test-uiSkill
- turbo-addSkill
- turbo-testSkill
- turbo-verifySkill
- which-prSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Start work on a new git branch, optionally in a new worktree.
- Very specific: line 41
If an issue has labels like bug → fix/, enhancement → feat/, documentation → docs/
- Distinctive: line 43
If a description starts with a semantic prefix, use it
- Very specific: line 44
Default to feat/ if unclear
- Very specific: line 61
When asked to start a new branch (no --worktree / -w flag):
- Distinctive: line 64
Run git status — if there are uncommitted changes, warn the user and stop
- Distinctive: line 65
Do NOT stash or discard changes automatically
- Very specific: line 73
If an issue number was given, fetch it: gh issue view <number> --json title,labels
- Very specific: line 86
When --worktree or -w is specified:
- Distinctive: line 98
Place as a sibling directory to the current repo
- Distinctive: line 122
NEVER force-delete branches or worktrees
- Distinctive: line 123
NEVER stash or discard uncommitted changes — always warn and stop
- Very specific: line 124
Always branch from origin/main (freshly fetched)
- Distinctive: line 125
If the branch name already exists, warn the user and ask what to do
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Branch
Start work on a new git branch, optionally in a new worktree.
Arguments
Accepts one of the following as arguments:
- Issue number: e.g.,
/branch 123— fetches the issue title and derives the branch name - Description: e.g.,
/branch add shellcheck support— derives the branch name from the text - Worktree flag: append
--worktreeor-wto create a git worktree instead of a regular branch
Examples:
/branch 123— branch from issue #123/branch add dark mode toggle— branch from description/branch 123 --worktree— worktree from issue #123/branch fix login redirect -w— worktree from description
Branch Naming
Derive the branch name using this format:
<type>/<issue-number?>-<slug>- type: Infer from context —
feat/,fix/,chore/,docs/,refactor/,perf/,test/,ci/- If an issue has labels like
bug→fix/,enhancement→feat/,documentation→docs/ - If a description starts with a semantic prefix, use it
- Default to
feat/if unclear
- If an issue has labels like
- issue-number: Include only if an issue number was provided
- slug: Lowercase, hyphenated, max ~50 chars, derived from the issue title or
description
- Strip filler words when too long
- e.g., "Add shellcheck support for shell scripts" →
add-shellcheck-support
Examples:
- Issue #123 titled "feat(cli): add watch mode" →
feat/123-add-watch-mode - Issue #45 labeled
bug, titled "Parser crashes on empty input" →fix/45-parser-crashes-on-empty-input - Description "add dark mode" →
feat/add-dark-mode - Description "fix: resolve null pointer" →
fix/resolve-null-pointer
Usage — Regular Branch
When asked to start a new branch (no --worktree / -w flag):
- Ensure clean state:
- Run
git status— if there are uncommitted changes, warn the user and stop - Do NOT stash or discard changes automatically
- Run
Fetch latest:
git fetch origin- Resolve branch name:
- If an issue number was given, fetch it:
gh issue view <number> --json title,labels - Derive the branch name per the naming rules above
- If an issue number was given, fetch it:
Create and switch to the branch:
git checkout -b <branch-name> origin/main- Confirm — Print the branch name and a summary of what was done
Usage — Worktree
When --worktree or -w is specified:
- Ensure clean state:
- Run
git status— if there are uncommitted changes, warn the user and stop
- Run
Fetch latest:
git fetch origin- Resolve branch name (same rules as above)
- Determine worktree path:
- Place as a sibling directory to the current repo
- Format:
<repo-dir>-<slug>(without the type prefix) - e.g., if repo is at
~/Code/py-lintroand branch isfeat/123-add-watch-mode:- Worktree path:
~/Code/py-lintro-123-add-watch-mode
- Worktree path:
- e.g., if branch is
fix/parser-crash:- Worktree path:
~/Code/py-lintro-parser-crash
- Worktree path:
Create the worktree:
git worktree add -b <branch-name> <worktree-path> origin/mainConfirm — Print the worktree path, branch name, and how to navigate there:
Created worktree at ~/Code/py-lintro-123-add-watch-mode Branch: feat/123-add-watch-mode (from origin/main) To start working: cd ~/Code/py-lintro-123-add-watch-mode
Important
- NEVER force-delete branches or worktrees
- NEVER stash or discard uncommitted changes — always warn and stop
- Always branch from
origin/main(freshly fetched) - If the branch name already exists, warn the user and ask what to do
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

