create-branch

Create Gitflow-convention git branches from story, epic, or task documents.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Gamaroff/agent-skills --skill create-branch-gamaroff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/Gamaroff/agent-skills/tree/main/skills/create-branch
Command: npx skills add https://github.com/Gamaroff/agent-skills --skill create-branch-gamaroff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually naming and basing git branches leads to inconsistent conventions and wrong base branches, especially in teams following Gitflow with stories, epics, hotfixes, and releases. This Skill automates branch creation with correct naming patterns and base-branch selection. ## Core Features & Use Cases - Automatic branch type detection: Accepts story files, epic files, task documents, raw descriptions, or explicit --hotfix/--release flags and derives the correct branch type and name. - Context-aware base branch selection: Detects sub-story relationships and epic integration branches, then prompts the user with recommended base options (develop, current feature branch, or epic integration branch). - Safety checks and worktree support: Halts on uncommitted changes, handles linked git worktrees, creates and pushes epic integration branches when needed, and cooperates with develop-pipeline locks. - Use Case: Run it with a story file like story.180.3.quick-re-search.md and get a properly named feature/story.180.3.quick-re-search branch cut from the right base, fetched and pushed to origin. ## Quick Start Ask the agent to create a branch from your story file, for example: create a branch for story.180.3.quick-re-search-functionality.md.

Frequently Asked Questions about create-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Gitflow feature branch from a story file?▼

Invoke the skill with the story file path, such as story.180.3.example-feature.md. It detects the story type, names the branch feature/story.<epic>.<story>.<name>, and prompts you to choose a base branch before creating and optionally pushing it.

How to create a hotfix or release branch with git?▼

Pass the --hotfix or --release flag with a version, for example --hotfix v1.2.1. Hotfix branches are cut from main and release branches from develop, following the hotfix/v<version> and release/v<version> naming patterns.

Can I create a branch when I have uncommitted changes?▼

The skill halts and shows uncommitted changes before branching. You can commit first, stash the changes with git stash push, or abort. A single implementation report file from the develop-story pipeline is allowed as an exception.

What is an epic integration branch and when is it used?▼

An epic integration branch (epic/<n>.<name>) is an opt-in branch declared in an epic's frontmatter via branch_model: epic-integration. All stories in that epic merge into it, and it reaches develop once as a single reviewed unit.

Why does branch creation fail inside a linked git worktree?▼

In a linked worktree the base branch is already checked out in the main worktree, so git checkout fails. The skill detects this and creates the feature branch directly from the fetched origin ref without checking out the base.