skills.rest
f4irline
f4irlineCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-branch-create

Generate convention-compliant git branch names from Linear ticket IDs.

5|Updated Jan 25, 2026
Search Tags:#git#workflow#validation#worktree#linear#branch#naming-convention
One-click install
npx skills add https://github.com/f4irline/bbqparty-ai --skill git-branch-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-branch-create
Source: https://github.com/f4irline/bbqparty-ai/tree/main/packages/opencode/.opencode/skills/git-branch-create
Command: npx skills add https://github.com/f4irline/bbqparty-ai --skill git-branch-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers and release workflows often produce inconsistent or poorly formatted branch names that break automation and make it hard to map work to tracking tickets; this Skill standardizes branch naming from Linear ticket IDs and avoids unsafe checkouts by returning the branch name for a worktree-based flow.

Core Features & Use Cases

  • Consistent Naming: Build branch names using the {type}/{ticket-id}-short-description pattern to enforce repository conventions.
  • Normalization & Validation: Produce a lowercase, hyphen-separated short description limited in length, sanitize special characters, and check remote refs to detect existing branches.
  • Safe Handoff: Intentionally does not checkout branches in the active workspace and returns branch state so callers can prepare or reuse a worktree.

Quick Start

Generate a branch name for ticket STU-15 with type feat and title Add user authentication.

Frequently Asked Questions about git-branch-create

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

FAQPage Schema
How do I generate a git branch name from a Linear ticket ID?▼

You generate a git branch name from a Linear ticket ID by resolving the ticket into a formatted string matching the {type}/{ticket-id}-short-description pattern, applying type selection and short-description normalization.

What is the best way to standardize git branch naming conventions for features and fixes?▼

Standardizing git branch naming conventions involves applying an automated format like {type}/{ticket-id}-short-description, which normalizes descriptions to lowercase hyphenated text and validates the type for releases.

Can I create a worktree branch without performing a git checkout in my active workspace?▼

Yes, you can create a worktree branch without a git checkout by returning the validated branch name and state to the caller, intentionally skipping the checkout step so you can safely prepare a separate worktree.

How does branch name normalization handle special characters and length limits?▼

Branch name normalization handles special characters and length limits by sanitizing the input text into a lowercase hyphen-separated short description, enforcing a maximum length while checking remote refs for existing branches.

What branch types are supported when formatting names for repository workflows?▼

Supported branch types when formatting names for repository workflows include features, fixes, refactors, docs, tests, chores, and performance updates, ensuring the generated branch name matches the correct ticket category.

Related Skills

Explore More Software Engineering Skills→
mostafa-drzmostafa-drz
2

get-up-to-speed

Aggregate git history, branch state, and Linear ticket context into a markdown briefing.

Community
Intermediate
homeassistant-aihomeassistant-ai
4.3k

wt

Create a git worktree under worktree/<branch> and update submodules.

Official
Intermediate
greyhaven-aigreyhaven-ai
29

grey-haven-linear-workflow

Automate Linear issue creation, branch naming, and PR integration with Git workflows.

Community
Basic
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate