creating-branch

Create standardized Git feature branches with incrementing names.

21|4|Updated Oct 24, 2025

Search Tags:#automation #git #conventional commits #branch #naming #sequential numbering

Ready to run

npx skills add https://github.com/joaquimscosta/arkhe-claude-plugins --skill creating-branch-joaquimscosta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: creating-branch
Source: https://github.com/joaquimscosta/arkhe-claude-plugins/tree/main/git/skills/creating-branch
Command: npx skills add https://github.com/joaquimscosta/arkhe-claude-plugins --skill creating-branch-joaquimscosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates descriptive, versioned branch names and supports optional spec-kit directories.

Core Features & Use Cases

Auto-detect type, sequential number, and keywords
Optional spec-kit integration to create pattern directories
Enforce concise, descriptive naming

Quick Start

Create a new feature branch with /create-branch and review the generated name.

Frequently Asked Questions about creating-branch

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

FAQPage Schema

How do I automate Git branch naming with sequential numbering?▼

Automate branch naming by detecting commit type (feat, fix, refactor, chore, docs), extracting keywords from your description, and generating incremented 3-digit numbers. The Skill assembles names as {type}/{number}-{keywords} and creates the branch with git checkout -b, ensuring consistent, readable naming across your team.

Can I generate branch names from uncommitted changes automatically?▼

Yes. The Skill auto-detects commit type and extracts 2–3 keywords from uncommitted changes or manual descriptions, then assigns the next sequential number. This works for feature additions, bug fixes, refactoring, and documentation work without requiring manual naming.

What branch naming convention does this follow?▼

Branch names follow the pattern {type}/{number}-{keywords}, where type is detected from conventional commit categories (feat, fix, refactor, chore, docs), number is a 3-digit global counter, and keywords are extracted from your description. This standardizes naming across Git workflows.

How does sequential numbering work across multiple branches?▼

The Skill maintains a global 3-digit counter that increments with each new branch created. This ensures every branch receives a unique, ordered number independent of type or keyword content, making it easy to track branch creation history.

Does this integrate with spec-kit for directory creation?▼

Yes. When spec-kit is installed, the Skill optionally creates a spec directory alongside branch creation, supporting pattern-based documentation and specification workflows within your Git repository structure.

What input validation happens to ensure valid branch names?▼

The Skill sanitizes inputs—including descriptions and extracted keywords—to ensure the final branch name complies with Git naming rules. Invalid characters are removed or replaced, preventing branch creation failures.