devops:branch

Create Git branches with structured naming conventions and source branch updates.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/atournayre/claude-personas --skill devops-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops:branch
Source: https://github.com/atournayre/claude-personas/tree/main/devops/skills/branch
Command: npx skills add https://github.com/atournayre/claude-personas --skill devops-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of Git branches following a structured workflow, ensuring consistency and reducing manual errors in version control.

Core Features & Use Cases

  • Structured Branching: Creates branches based on issue numbers or descriptive text, adhering to common naming conventions (feature, fix, chore, etc.).
  • Source Branch Management: Automatically determines the source branch, pulling the latest changes before branching.
  • Use Case: When starting a new feature, you can run /devops:branch 123 to create a feature/123-description branch from your main development branch, ensuring you're up-to-date.

Quick Start

Create a new git branch named 'feature/123-user-authentication' from the 'develop' branch.

Frequently Asked Questions about devops:branch

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

FAQPage Schema
How do I create Git branches with structured naming conventions automatically?

To create Git branches with structured naming conventions, you can automate the process using an issue number or descriptive text. This ensures consistent prefixes like feature, fix, hotfix, chore, docs, and test are applied automatically.

What's the best way to manage source branches before creating a new Git branch?

Managing source branches involves automatically resolving the target base and pulling the latest changes before branching. This workflow guarantees your new branch is created from an up-to-date state, preventing integration conflicts.

Can I use issue numbers to generate feature branches in Git?

Yes, you can use issue numbers to generate feature branches in Git. By passing an issue number, the workflow automatically creates a structured branch name like feature/123-description, linking your version control directly to your tracking system.

Does this branching workflow support different branch types like hotfix and chore?

This branching workflow supports feature, fix, hotfix, chore, docs, and test branch types. It automatically detects the required prefix based on your input, ensuring your version control strategy adheres to standard conventions.

How does branch existence validation work before creating a new Git branch?

Branch existence validation checks the repository before creating a new Git branch to prevent duplicates. This mechanism ensures you do not accidentally overwrite existing work or create conflicting branches in your version control system.