git-branch
Skill1 starsChanged 7 months agoMITView on GitHub
Create Git branches with automatic type detection and project-specific naming conventions. Use when asked to "create a branch", "make a new branch", "create branch for changes", or when ready to organize code changes into a new branch. Supports feat, fix, docs, refactor, test, build, ci, chore, revert, and perf branch types with automatic type selection based on changed file patterns.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/devsquad-copilottheir own version, first seen Oct 16, 2026
- my-chiefmind/ai-maestrotheir own version, first seen Oct 13, 2026
- cognis-digital/skillsmiththeir own version, first seen Oct 11, 2026
- mir-am/skills-agents-ai-codingtheir own version, first seen Oct 1, 2026
- ZunoSmartLabs/zsl-superpowerstheir own version, first seen Sep 21, 2026
- CarpeWu/claude-git-skillstheir own version, first seen Jan 27, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- microsoft/devsquad-copilot★ 50same name
- my-chiefmind/ai-maestro★ 6same name
- mir-am/skills-agents-ai-coding★ 2same name
- ZunoSmartLabs/zsl-superpowers★ 2same name
- CarpeWu/claude-git-skills★ 0same name
- cognis-digital/skillsmith★ 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 repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- gh-default-branchSkill
- gh-prSkill
- git-branchSkill
- git-commitSkill
- gh-default-branchSkill
- gh-prSkill
- git-commitSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when:
- Distinctive: line 21
Use the following command to view staged changes:
- Distinctive: line 27
Important: If there are staged changes, proceed to the next step.
- Distinctive: line 29
If there are no staged changes, check unstaged changes with:
- Distinctive: line 43
If there are only staged changes, base the branch name on the staged changes.
- Distinctive: line 44
If there are only unstaged changes, base the branch name on the unstaged changes.
- Distinctive: line 45
If there are both staged and unstaged changes, base the branch name on the staged changes.
- Distinctive: line 60
description: should concisely describe the changes made, using hyphens to separate words.
- Distinctive: line 64
Use git switch -c to create and switch to the new branch.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Git Branch Skill
This skill guides the creation of Git branches with project-specific naming conventions.
When to Use
Use this skill when:
- You have made changes to the codebase and need to create a new branch for those changes.
- You want to ensure that the branch name follows the project's naming conventions.
Instructions
Step 1: Check staged changes
Use the following command to view staged changes:
git diff --stagedImportant If there are staged changes, proceed to the next step.
If there are no staged changes, check unstaged changes with:
git diff --name-onlyStep 2: Determine branch type and description
The format for branch names is:
<type>-<description>- If there are only staged changes, base the branch name on the staged changes.
- If there are only unstaged changes, base the branch name on the unstaged changes.
- If there are both staged and unstaged changes, base the branch name on the staged changes.
type is determined based on the patterns of the changed files:
feat-: New features or changes to existing featuresfix-: Bug fixesrefactor-: Refactoring (changes that do not add features or fix bugs)test-: Adding or modifying tests (e.g., changes to*.spec.*or*.spec.*.snapfiles)docs-: Documentation-only changes (e.g., changes to*.mdfiles)ci-: CI-related changes (e.g., changes to files in.github/workflows/*or.github/actions/*)chore-: Other changes (e.g., changes to*.json, configuration files like*.config.js,.gitignore, etc.)revert-: Reverting previous commitsbuild-: Changes related to the build system or external dependenciesperf-: Performance improvements
description should concisely describe the changes made, using hyphens to separate words.
Step 3: Create the branch
Use git switch -c to create and switch to the new branch.
Example:
git switch -c feat-user-authentication[!NOTE]
When the name of the branch already exists, append a unique suffix to the branch name to avoid conflicts. For example, if
feat-user-authenticationalready exists, createfeat-user-authentication-1,feat-user-authentication-2, etc.
References
- branch-name.md
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.

