git-flow-branch-creator

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

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tamago0224/kuroshio-mta --skill git-flow-branch-creator-tamago0224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-flow-branch-creator
Source: https://github.com/tamago0224/kuroshio-mta/tree/main/.agents/skills/git-flow-branch-creator
Command: npx skills add https://github.com/tamago0224/kuroshio-mta --skill git-flow-branch-creator-tamago0224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to decide which Git Flow branch type to use and how to name it correctly based on the nature of their changes, leading to inconsistent workflows and extra manual effort.

Core Features & Use Cases

  • Automated analysis of git status and git diff output to determine the appropriate branch type (feature, release, or hotfix).
  • Semantic branch name generation that follows Git Flow naming conventions and avoids naming conflicts.
  • Automatic branch creation from the correct base branch and immediate checkout.
  • Use case: A developer finishes a set of UI enhancements and wants the tool to create a properly named feature branch without manually deciding the name or base.

Quick Start

Run the Git Flow Branch Creator to analyze your current git changes and automatically create the suitable branch.

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 current changes?

You can automatically create a Git Flow branch by running the tool to analyze your git status and diff output, which determines the correct branch type and generates a semantic name before checking it out.

How does git diff analysis determine whether I need a feature, release, or hotfix branch?

Git diff analysis evaluates your code changes to classify the modification type, automatically determining whether a feature, release, or hotfix branch is required for your specific development workflow.

What is the best way to generate semantic Git Flow branch names and avoid naming conflicts?

Generating semantic Git Flow branch names automatically analyzes your repository changes to produce convention-compliant names while checking existing branches to prevent naming conflicts during creation.

Do I need to manually specify the base branch when creating a feature or hotfix branch?

You do not need to manually specify the base branch because the tool automatically determines and branches from the correct base, ensuring proper Git Flow hierarchy for feature, release, and hotfix branches.

Can I use this Git Flow automation in an existing repository with mixed uncommitted changes?

You can use this Git Flow automation in repositories with uncommitted changes because it directly analyzes your current git status and diff output to determine the appropriate branch type and semantic name.

Why does my automated Git Flow branch creation fail due to naming conflicts?

Automated Git Flow branch creation avoids naming conflicts by generating semantic names that follow Git Flow conventions and checking against existing branches to ensure uniqueness before checkout.