skills.rest
Brave-Labs
Brave-LabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Dev10x-ticket-branch

Generate git branches from ticket IDs with worktree-aware naming.

Updated Aug 27, 2026
Search Tags:#git#workflow#development#worktree#ticket#branch#branch-name
One-click install
npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-ticket-branch-brave-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Dev10x-ticket-branch
Source: https://github.com/Brave-Labs/dev10x/tree/main/codex-skills/dev10x-ticket-branch
Command: npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-ticket-branch-brave-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating branches for tickets often results in inconsistent names, stale bases, or confusion when working in Git worktrees. This skill enforces project conventions, ensures you’re on the latest develop, and automatically includes worktree context when needed.

Core Features & Use Cases

  • Validates git state and fetches the latest develop before branching.
  • Generates a standardized branch name from the ticket ID, title, and optional worktree.
  • Detects worktrees and includes the worktree name in the branch path to keep branches organized across environments.
  • Supports starting work on new tickets with consistent naming across regular repos and worktrees. Use Case: A developer runs this with PAY-133: Fix login timeout to create janusz/PAY-133/fix-login-timeout or janusz/PAY-133/tt-pos-7/fix-login-timeout in a worktree.

Quick Start

Provide the ticket ID and title, and let the skill generate and checkout the properly named branch from the latest develop.

Frequently Asked Questions about Dev10x-ticket-branch

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

FAQPage Schema
How do I create a git branch from a ticket ID with consistent naming?▼

To create a git branch from a ticket, this skill validates the repository state, fetches the latest develop, and generates a standardized branch name in the username/TICKET-ID/slug format.

What is the best way to name git branches when working in worktrees?▼

Naming git branches in worktrees requires including the worktree context. This skill detects active worktrees and appends the worktree name to the branch path, creating a structured username/TICKET-ID/worktree/slug format.

Can I automatically fetch the latest develop before creating a new ticket branch?▼

Yes, you can automatically fetch the latest develop before creating a ticket branch. The skill validates your current git state and updates develop to ensure your new branch starts from a fresh, up-to-date base.

Does this branch naming skill require a specific git workflow setup?▼

This branch naming skill requires a standard git workflow setup using a develop branch. It validates the repository state to ensure clean working conditions before fetching updates and generating the ticket branch.

Why does my git ticket branch include a worktree name in the path?▼

Your git ticket branch includes a worktree name in the path because the skill detects active worktrees and incorporates that name into the branch path to keep branches organized across different working environments.

Related Skills

Explore More Software Engineering Skills→
Dev10x-GuruDev10x-Guru
7

Dev10x:ticket-branch

Create Git branches for tickets using username, ticket ID, and worktree name.

Official
Intermediate
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
thomfilgthomfilg

cleanup-worktrees

Clean up git worktrees after verifying merged code and Done/Closed ticket tasks.

Community
Advanced
iani-kuliiani-kuli

create-branch

Create git branches with standardized names from user identity and diffs.

Community
Intermediate