branch

Create Git feature branches with project-specific naming conventions and safety checks.

Updated Feb 24, 2026

Search Tags:#git #developer tools #version control #workflow automation #branching

Ready to run

npx skills add https://github.com/metalspawn/claude-ops --skill branch-metalspawn

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Git branches, ensuring consistency with project naming conventions and preventing accidental work on protected branches.

Core Features & Use Cases

Automated Branch Naming: Generates branch names based on ticket IDs, keywords (fix, feat, refactor, etc.), and descriptive slugs.
Convention Adherence: Prioritizes project-specific branch naming rules found in CLAUDE.md.
Safety Checks: Prevents branch creation on protected branches (main, master, develop) and warns if a branch already exists.
Use Case: When starting a new feature, you can simply run /orc:branch --ticket JIRA-123 Implement user authentication and the skill will create a branch named feat/JIRA-123-implement-user-authentication.

Quick Start

Create a new feature branch for ticket JIRA-123 with the description Implement user authentication.

Frequently Asked Questions about branch

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

FAQPage Schema

How do I create a Git feature branch with consistent naming conventions?▼

Automated Git branch creation applies project-specific or default naming conventions by inferring branch types from keywords and generating descriptive slugs. This ensures consistent branch names without manual formatting.

Can I include a JIRA ticket reference when creating a version control branch?▼

Yes, you can include ticket references when creating a version control branch. The tool handles ticket IDs and integrates them directly into the generated branch name alongside a descriptive slug based on your input.

How does branch type inference work for Git workflow automation?▼

Branch type inference for Git workflow automation works by detecting specific keywords like fix, feat, or refactor in your input. It uses these keywords to automatically prefix your branch with the appropriate type label.

Does branch creation prevent operations on protected branches like main or master?▼

Yes, branch creation includes safety checks that prevent operations on protected branches such as main, master, and develop. It also warns you if a branch with the same name already exists to avoid conflicts.

What is the best way to enforce custom Git branch naming rules across a project?▼

To enforce custom Git branch naming rules, you can define project-specific conventions in a CLAUDE.md file. The branch creation process prioritizes these rules to ensure all generated branch names match your team's standards.