git-flow-branch-creator

Analyze git status and diff to create semantic Git Flow branches.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill git-flow-branch-creator-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-flow-branch-creator
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/git-flow-branch-creator
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill git-flow-branch-creator-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes uncommitted and staged repository changes to determine the correct Git Flow branch type and generates a semantic branch name, removing uncertainty and manual naming errors when starting work, preparing releases, or fixing production issues.

Core Features & Use Cases

  • Change analysis: Inspect git status and git diff outputs to understand the nature and scope of modifications.
  • Branch classification: Map changes to feature, release, or hotfix according to the Git Flow model and edge-case handling for mixed changes.
  • Automated naming & creation: Generate kebab-case, descriptive branch names, validate conflicts with existing branches, and create/switch to the new branch.
  • Use Case: A developer with staged changes that add a new API endpoint runs the Skill to produce a branch like feature/add-user-endpoint from develop and receive guidance on next steps.

Quick Start

Analyze the current git status and diff to determine the best Git Flow branch type and create the branch automatically.

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 create a Git Flow branch automatically from my staged changes?

The Skill determines the correct Git Flow branch type by analyzing modified files and diff content. It maps uncommitted and staged changes to feature, release, or hotfix categories, handling edge cases for mixed changes according to the Git Flow model.

Can I generate semantic branch names directly from git diff content?

Yes, you can generate semantic branch names from git diff content. The Skill inspects staged modifications to produce descriptive, kebab-case branch names following Git Flow conventions, removing manual naming errors and uncertainty.

Does this branching tool validate conflicts with existing Git Flow branches?

Yes, this branching tool validates conflicts with existing Git Flow branches. After determining the branch type and generating a name from your repository changes, it checks against existing branches before safely creating and switching to the new branch.

What is the best way to classify uncommitted changes as feature, release, or hotfix?

The best way to classify uncommitted changes as feature, release, or hotfix is by analyzing git status and git diff outputs. This maps modifications to the correct Git Flow branch type automatically before committing and pushing.

How do I handle mixed changes when choosing a source branch for Git Flow?

To handle mixed changes when choosing a source branch for Git Flow, the Skill applies edge-case handling logic during classification. It analyzes modified files and diff content to determine the dominant branch type and selects the correct source branch accordingly.