git-flow-branch-creator

Analyze git status and diff to create Git Flow branches.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork of deciding whether your changes should go into a feature, release, or hotfix branch and what the branch name should be under Git Flow.

Core Features & Use Cases

  • Change-aware branch type selection: Classifies modifications by inspecting git status and the relevant diff (git diff or git diff --cached).
  • Git Flow compliant naming: Generates a semantic branch name that follows the nvie Git Flow conventions (feature, release, hotfix).
  • Automated branch creation: Creates the branch from the appropriate base branch (develop or master) and switches to it.

Use case: When you finish a new task (like adding a user-facing improvement or a new API endpoint), it helps you reliably create a feature/... branch with a descriptive name; when you fix a critical production issue, it guides you toward a hotfix/... branch.

Quick Start

Run the prompt and let it analyze your current git changes (status and diff) to propose and create the appropriate Git Flow 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 create a Git Flow branch from my current changes?

To create a Git Flow branch, the Skill analyzes your current repository changes via git status and git diff to determine the correct branch type and semantic name, then automatically creates and switches to the branch.

How does Git Flow branching decide between feature, release, and hotfix branches?

Git Flow branching classifies modifications by inspecting the nature and urgency of file modifications through git status and diff outputs, matching changes to feature development, release preparation, or critical hotfix scenarios.

Can I use this to generate convention-compliant semantic branch names automatically?

Yes, it generates convention-compliant semantic branch names by following nvie Git Flow conventions, ensuring your feature, release, and hotfix branches are named correctly before creation.

Do I need to manually specify the base branch when starting a Git Flow hotfix?

No, you do not need to manually specify the base branch, because the Skill applies Git Flow rules for branching origins to automatically create hotfix branches from master and feature branches from develop.

What is the best way to handle release preparation branches in Git Flow?

The best way to handle release preparation branches is to let the Skill analyze your staged and unstaged diffs to identify release-level changes and automatically generate a compliant release branch from the develop base.

Why does my Git Flow branch creation fail when I have uncommitted changes?

Git Flow branch creation relies on analyzing your repository modifications through git diff and git status, so if there are no tracked file changes or diffs to inspect, the Skill cannot determine the correct branch type.