create-branch
Skill17 starsChanged 9 months agoMITView on GitHub
Generate a branch name from current changes and create it if on main. Use when starting new work and need a properly named feature branch.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Pubx-ai/skillstheir own version, first seen Nov 8, 2026
- AgnesAI-Labs/agnet-skills-cntheir own version, first seen Nov 1, 2026
- Alvolutionor/delivery-workflow-skillstheir own version, first seen Oct 17, 2026
- matthewyuh246/Claude_Skillstheir own version, first seen Oct 11, 2026
- Emiyaaaaa/clay-uitheir own version, first seen Oct 8, 2026
- getsentry/skillstheir own version, first seen Jul 25, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- getsentry/skills★ 1.1ksame name
- Emiyaaaaa/clay-ui★ 1.1ksame name
- Pubx-ai/skills★ 6same name
- AgnesAI-Labs/agnet-skills-cn★ 1same name
- Alvolutionor/delivery-workflow-skills★ 0same name
- matthewyuh246/Claude_Skills★ 0same name
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 repository12 other files it gives its agents.
- commitSkill
- create-prSkill
- create-skillSkill
- fix-ciSkill
- gh-issueSkill
- merge-to-stagingSkill
- review-pr-commentsSkill
- slack-pr-recapSkill
- start-working-on-issueSkill
- test-coverage-improveSkill
- testing-guideSkill
- ui-patternsSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Run git status to see which files are modified/added/deleted
- Distinctive: line 19
Run git diff to understand what the changes do
- Distinctive: line 20
If there are staged changes, also run git diff --cached
- Distinctive: line 33
Keep total length under 50 characters
- Very specific: line 41
If on main: run git checkout -b <branch-name>
- Distinctive: line 42
If NOT on main: just output the suggested branch name and explain you're not on main
- Distinctive: line 45
Run git branch --show-current to verify you're on the new branch
- Distinctive: line 51
Keep branch names concise but descriptive
- Distinctive: line 52
Never include issue numbers unless explicitly asked
“Common” is measured: kept by at least 6 in 10 of the 5 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
Create Branch from Changes
You are tasked with generating a meaningful branch name based on the current uncommitted changes.
Process:
- Check current branch:
- Run
git branch --show-current - Note whether you're on
mainor another branch
- Run
- Analyze the changes:
- Run
git statusto see which files are modified/added/deleted - Run
git diffto understand what the changes do - If there are staged changes, also run
git diff --cached
- Run
- Generate a branch name:
- Use format:
<type>-<short-description> - Types (from Conventional Commits):
feat- new featurefix- bug fixrefactor- code restructuringdocs- documentation onlychore- maintenance taskstest- adding/updating testsstyle- formatting, no code change
- Description: 2-4 words, kebab-case, lowercase
- Keep total length under 50 characters
- Examples:
feat-add-user-dashboardfix-login-validationrefactor-api-handlersdocs-update-readme
- Use format:
- Create the branch (if on main):
- If on
main: rungit checkout -b <branch-name> - If NOT on
main: just output the suggested branch name and explain you're not on main
- If on
- Confirm success:
- Run
git branch --show-currentto verify you're on the new branch - Tell me the branch name created
- Run
Important:
- Analyze the actual content of changes, not just file names
- Choose the most appropriate type based on what the changes do
- Keep branch names concise but descriptive
- Never include issue numbers unless explicitly asked
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.