create-branch

Create git branches with standardized names from user identity and diffs.

Updated May 5, 2026

Search Tags:#automation #git #workflow #branching #developer-tools #sentry

Ready to run

npx skills add https://github.com/iani-kuli/harness_bro --skill create-branch-iani-kuli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/ported/create-branch
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill create-branch-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates manual naming errors and inconsistency in git workflows by automatically generating branch names that adhere to established organizational standards.

Core Features & Use Cases

Automated Naming: Derives branch names using user identity, branch type, and a short description of the work.
Context Awareness: Automatically detects the appropriate base branch and handles naming collisions by appending version numbers.
Use Case: When starting a new feature, simply invoke the skill to have it analyze your current git status, determine the correct prefix, and create a properly formatted branch without manual input.

Quick Start

Use the create-branch skill to start a new feature branch based on my current changes.

Frequently Asked Questions about create-branch

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

FAQPage Schema

How do I automate git branch creation to follow standardized naming conventions?▼

Automated git branch creation standardizes naming by deriving branch names from your user identity, work context, and local diffs. It analyzes your git status to determine the correct prefix and executes checkout commands without manual input.

What is the best way to generate a git feature branch name from my current changes?▼

Generating a git feature branch name from current changes uses your git configuration and local diffs to derive a properly formatted name. It detects the appropriate base branch and handles naming collisions by automatically appending version numbers.

Do I need git CLI access to use automated branching workflows?▼

Git CLI access is required for automated branching workflows. The process relies on standard shell utilities and git CLI commands to resolve branch metadata, analyze local diffs, and execute the checkout operations needed to create branches.

How does automated branch naming handle naming collisions in git?▼

Automated branch naming handles git naming collisions by appending version numbers to the generated branch name. It automatically detects existing branches and resolves conflicts to maintain consistent repository maintenance without manual intervention.

Why do my git branch names lack consistency across different repository contributors?▼

Git branch names lack consistency due to manual naming errors and varying individual conventions. Automating branch creation eliminates these errors by enforcing organizational standards, deriving names from user identity and work context.