create-branch

Create GitFlow feature, release, and hotfix branches with validated naming.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/taiga-K/awesome-backend-template --skill create-branch-taiga-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/taiga-K/awesome-backend-template/tree/main/.cursor/skills/create-branch
Command: npx skills add https://github.com/taiga-K/awesome-backend-template --skill create-branch-taiga-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation and switching of Git branches according to GitFlow conventions, reducing manual errors from incorrect parent selection or inconsistent branch naming during feature, release, and hotfix workflows.

Core Features & Use Cases

  • GitFlow-compliant branch creation: Create feature, release, and hotfix branches with the correct parent branch selected.
  • Context switching: Optionally switch the working branch to the newly created branch after creation.
  • Procedure-driven enforcement: Reads repository-specific rules to enforce naming patterns and parent branch rules for consistency.
  • Use Case: When preparing a release candidate, generate a release branch from develop that follows naming rules and immediately switch the workspace to that branch.

Quick Start

Create a new feature branch named feature/user-auth from develop while following the repository's GitFlow rules and referenced procedure file.

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 Git branch following GitFlow conventions?

To create a GitFlow branch, you need to select the correct parent branch and apply specific naming patterns for feature, release, or hotfix workflows. This skill automates that by validating parent selection and enforcing repository-specific naming rules before creating the branch.

When should I branch from develop instead of main in a GitFlow workflow?

In a GitFlow workflow, you branch from develop for new features and release preparations, while hotfix branches stem from main. This skill validates the correct parent branch selection automatically based on the specific branch type you intend to create.

How do I enforce consistent naming patterns for feature and release branches?

Enforcing consistent naming patterns for feature and release branches requires reading repository-specific rules before execution. This skill reads a reference procedure file to validate and apply branch-name patterns, preventing inconsistent naming during development and release preparation.

Can I automatically switch to a newly created feature branch in Git?

Yes, you can automatically switch your working branch to the newly created feature branch immediately after creation. This skill supports context switching as an optional step, moving your workspace directly to the new GitFlow branch.

What is the best way to create a hotfix branch for an emergency release?

Creating a hotfix branch for an emergency release requires branching from main and applying strict naming conventions to track the fix. This skill enforces these GitFlow rules and validates the parent branch to ensure hotfix integrity.

Does this branch creation skill require any specific Git repository setup?

Yes, the skill requires a reference file located at .agents/skills/create-branch/SKILL.md within the repository. It reads this file before executing to extract and enforce repository-specific GitFlow rules and naming patterns.