bp-branch

Create kebab-case feature branches from type and description inputs.

4|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skaisser/blueprint --skill bp-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bp-branch
Source: https://github.com/skaisser/blueprint/tree/main/skills/bp-branch
Command: npx skills add https://github.com/skaisser/blueprint --skill bp-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating new feature branches can be error-prone when naming conventions aren't enforced or bases aren't consistently selected. This skill ensures branches follow a standardized type/description format and start from the correct base.

Core Features & Use Cases

  • Enforces kebab-case naming for new branches based on type/description.
  • Supports common branch types (feat, fix, docs, etc.) and ensures valid formatting.
  • Base-branch selection logic (use staging if present, otherwise main) to keep branches aligned with the team workflow.

Quick Start

Create a new branch using the required type/description format, e.g., feat/login-flow.

Frequently Asked Questions about bp-branch

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

FAQPage Schema
How do I create a kebab-case feature branch in git?

The skill automatically selects the base branch by checking for a staging branch first, using it if present, and falling back to main otherwise to keep new branches aligned with team workflows.

What branch types can I use when creating a new git branch?

No, you cannot use arbitrary branch names. The skill enforces standardized type and description formats, validating against allowed types to prevent invalid branch creation.

How do I ensure my git branch names follow team naming conventions?

To ensure git branch names follow team conventions, the skill enforces a standardized type/description format. It validates the resulting kebab-case name against allowed types before creation.

How does the branch base get selected when starting a new feature branch?

The base branch is selected by checking for a staging branch first and falling back to main if staging is not available. This logic keeps new feature branches aligned with the team workflow.

What happens if I enter an invalid format for a feature branch name?

If you enter an invalid format for a feature branch name, the skill validates the resulting branch name and blocks the creation. This enforces allowed types and formats to prevent unsafe branches.