git-flow-branch-creator

Analyzes git status and diff output to create Git Flow branches with semantic names.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill git-flow-branch-creator-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-flow-branch-creator
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/git-flow-branch-creator
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill git-flow-branch-creator-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the correct branch type and name under the Git Flow model is error-prone and inconsistent across teams. This Skill inspects your current uncommitted changes and automatically determines whether they belong on a feature, release, or hotfix branch, then creates it with a conventional name. ## Core Features & Use Cases - Change Analysis: Runs git status and git diff to classify changes as features, release preparation, or critical hotfixes using a structured decision framework. - Semantic Branch Naming: Generates kebab-case branch names following Git Flow conventions such as feature/user-authentication, release-2.1.0, or hotfix/security-patch. - Edge Case Handling: Covers mixed changes, empty working trees, existing branches, and naming conflicts with fallback suggestions. - Use Case: A developer finishes fixing a production security bug and runs the Skill; it detects the critical nature of the diff and creates hotfix/auth-security-patch from master automatically. ## Quick Start Ask the assistant to analyze my current git changes and create the appropriate Git Flow branch for them.

Frequently Asked Questions about git-flow-branch-creator

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

FAQPage Schema
How do I automatically create a Git Flow branch from my changes?

Run the Skill with uncommitted changes in your working tree. It executes git status and git diff, classifies the changes as feature, release, or hotfix work, then creates and switches to a semantically named branch from the correct source branch.

What branch naming conventions does Git Flow use?

Feature branches use feature/descriptive-name, release branches use release-X.Y.Z, and hotfix branches use hotfix-X.Y.Z or hotfix/critical-description. Names use lowercase kebab-case and may include ticket numbers for context.

How does it decide between feature, release, and hotfix branches?

It applies a decision tree: critical production fixes become hotfixes branched from master, version bumps and release preparation become release branches from develop, and everything else defaults to feature branches from develop.

What happens if the suggested branch name already exists?

The Skill detects naming conflicts and appends an incremental suffix or proposes alternative names. It also offers two to three fallback branch name suggestions if the primary suggestion is unsuitable.

Can it handle mixed changes like features combined with bug fixes?

Yes, mixed changes are a documented edge case. The Skill prioritizes the most significant change type or recommends splitting the work into multiple branches to keep each branch focused.