create-branch

Name: create-branch
Availability: InStock
Author: Sentry

Create git branches with Sentry naming conventions from work descriptions.

905|47|Updated Jan 5, 2026

Search Tags:#git #workflow #branching #branch #sentry #naming

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines creating git branches that adhere to Sentry naming conventions, reducing human error and confusion.

Core Features & Use Cases

Automated prefix resolution: Automatically determines a branch prefix from user context and repo conventions.
Description-driven naming: Uses the provided work description to generate a meaningful short description in kebab-case.
Safe base selection: Branches are created from the appropriate base branch without switching default without explicit user instruction.
Collision handling: Appends -2, -3 to avoid conflicts.

Quick Start

Tell the tool what you want to name the work and it will create and switch to the new branch following Sentry 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 a git branch that follows Sentry naming conventions automatically?▼

To create a git branch following Sentry naming conventions, provide a work description and the tool classifies the branch type, generates a kebab-case short description, and creates the branch from the appropriate base without prompting.

What is the best way to automate git branch prefix resolution for feature or bugfix workflows?▼

Automating git branch prefix resolution involves detecting the work prefix from user context and repo conventions, classifying the branch type, and generating a compliant kebab-case name to prevent naming drift across feature, bugfix, or maintenance workflows.

How does collision handling work when generating a kebab-case git branch name?▼

Collision handling for kebab-case git branch names appends sequential suffixes like -2 or -3 to avoid conflicts, ensuring the generated branch name remains unique without requiring manual user intervention.

Can I use description-driven naming to create a maintenance branch without switching the default base?▼

Yes, description-driven naming creates a maintenance branch safely from the appropriate base without switching the default base, requiring only the provided work description to generate the meaningful kebab-case short name.

Does the Sentry branching workflow support creating a branch when changes are detected automatically?▼

Yes, the Sentry branching workflow works when the user describes the work or when changes are detected, automatically resolving the prefix and creating the compliant git branch without explicit prompting.

Why should I use kebab-case short descriptions for git branch naming?▼

Using kebab-case short descriptions for git branch naming prevents human error and naming drift, ensuring branches adhere to Sentry conventions and maintain clear, consistent formatting across any repository.