creating-branch

Create a feature branch from the current Git state with conventional naming.

5|4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/cblecker/claude-plugins --skill creating-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-branch
Source: https://github.com/cblecker/claude-plugins/tree/main/plugins/git-workflows/skills/creating-branch
Command: npx skills add https://github.com/cblecker/claude-plugins --skill creating-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual overhead and potential inconsistencies of creating new git feature branches. It ensures your working tree is clean, your base branch is synchronized, and your new branch follows conventional naming, letting you jump straight into development.

Core Features & Use Cases

  • Structured Branch Creation: Follows a guided workflow to create new feature branches from a clean, synchronized mainline.
  • Conventional Naming: Automatically generates or validates branch names based on conventional standards.
  • Stashing Support: Handles uncommitted changes by offering to stash them, ensuring a clean state before branch creation.
  • Use Case: When you're ready to start a new task, simply ask to "create a branch for adding user authentication," and this Skill will set up your environment perfectly, based on the latest code.

Quick Start

Create a new feature branch for 'implementing the new search algorithm'.

Frequently Asked Questions about creating-branch

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

FAQPage Schema
How do I create a Git feature branch with conventional naming?

Feature branch creation automatically generates kebab-case names following conventional-commit prefixes from your request text. The Skill identifies your mainline, creates the branch from that base, and checks it out, ensuring your branch name follows standard conventions without manual formatting.

What happens to uncommitted changes when I create a new branch?

Uncommitted changes are preserved through stashing before branch creation. The Skill offers to stash your work, ensuring a clean working tree while keeping your changes safe, then checks out your new branch so you can resume development.

How does the Skill prevent branch naming conflicts?

Branch creation enforces uniqueness by detecting existing branches with the same name. When conflicts occur, the Skill proposes alternatives using suffix-based disambiguation, letting you choose a unique branch name without manual renaming.

Can I use this for any Git workflow or are there restrictions?

Mainline protection is enforced, so you cannot create branches directly on protected base branches like main or master. The Skill identifies your project's mainline automatically, ensuring branch creation follows your repository's protection rules.

Do I need to manually specify the base branch or does the Skill detect it?

Base branch detection is automatic through a mainline-detection script that runs to identify your project's primary branch. You can also specify a base branch in your request, and the Skill will create your feature branch from that target instead.