
Git Flow Branch Creator
Inspects your git changes and creates a correctly named Git Flow branch for them
- Repository
- github/awesome-copilot
- Stars
- 40,703
- Licence
- MIT
- Files
- 1 file
What it does
When you ask the agent to start work on your uncommitted changes, it runs git status and git diff to read what changed, then decides whether the work belongs on a feature, release, or hotfix branch under the nvie Git Flow model. It proposes a kebab-case branch name, creates the branch, switches to it, and summarizes its reasoning. This saves you from picking the branch type and name by hand.
Great for
- Developers who use Git Flow and want consistent branch names
- Teams that want branch naming to follow the same conventions across contributors
- Anyone who regularly forgets to create a branch before editing code
Skip it if
- Projects that do not use Git Flow (e.g. trunk-based or GitHub Flow), because the branch types and names will not match their workflow
- Hotfix decisions on production systems without human review, since the classification is heuristic and a wrong branch type can cause a bad release path
Try asking
- “Create the right Git Flow branch for my current uncommitted changes”
- “Look at my staged changes and name a branch for them”
- “I fixed a security bug in authentication, make the right hotfix branch”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
git-flow-branch-creator.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip git-flow-branch-creator.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip git-flow-branch-creator.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Stage only the changes you want on the branch before asking, so git diff --cached reflects the intended scope
- Check the proposed branch type before confirming, especially for hotfix and release, since the skill infers these from the diff
- If your changes mix features and fixes, ask the agent to split them into separate branches rather than accepting one combined branch
What's inside
- SKILL.md
Redistributed unmodified from github/awesome-copilot under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.