create-branch

Name: create-branch
Availability: InStock
Author: yanochka11

Create standardized git branches using repository naming conventions and change types.

Updated May 5, 2026

Search Tags:#automation #git #workflow #version control #github #branch

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually naming and creating git branches by applying consistent conventions and selecting appropriate branch bases automatically.

Core Features & Use Cases

Branch Naming Automation: Generates standardized branch names using user identity, work descriptions, and change types.
Repository-Aware Workflow: Detects branch context, remote defaults, collisions, and suitable starting points before creating branches.
Use Case: When beginning a new feature or fix in a repository, use this Skill to create a properly formatted branch without manually deciding the naming pattern.

Quick Start

Use the create-branch skill to create a new branch for the current work following the repository naming conventions.

Frequently Asked Questions about create-branch

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

FAQPage Schema

How do I create consistent git branches automatically?▼

To create consistent git branches automatically, this Skill inspects repository metadata and applies naming conventions to generate standardized branch names. It classifies the branch type, detects collisions, and creates the branch from a suitable starting point without manual naming decisions.

Does this branch naming automation work with existing GitHub repository conventions?▼

Yes, this branch naming automation works with GitHub repository conventions by detecting remote defaults and branch context. It analyzes repository changes and work descriptions to generate names that align with your existing version control workflow.

What's the best way to standardize feature and fix branch names in version control?▼

The best way to standardize feature and fix branch names in version control is using a Skill that applies consistent conventions automatically. It uses user identity, work descriptions, and change types to generate properly formatted branches for maintenance tasks and collaborative workflows.

How does automatic branch creation handle naming collisions?▼

Automatic branch creation handles naming collisions by inspecting repository metadata and applying collision handling logic before creating the branch. This ensures the generated branch name does not conflict with existing branches in the version control system.

Can I use this Skill for both feature work and maintenance fixes?▼

Yes, you can use this Skill for both feature work and maintenance fixes. It applies branch type classification to determine the appropriate naming pattern based on the detected repository changes, supporting diverse software development workflows.

Do I need to manually specify a base branch when creating a new git branch?▼

No, you do not need to manually specify a base branch. The Skill detects suitable starting points and remote defaults automatically by inspecting git metadata, selecting an appropriate base before creating the new standardized branch.