Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

git-branch-create

Estrellas4

Forks0

Actualizado15 de febrero de 2026 a las 18:50

Resolve a properly named git branch from a Linear ticket ID following the convention {type}/{ticket-id}-short-description

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

f4irline

f4irline/bbqparty-ai

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	git-branch-create
description	Resolve a properly named git branch from a Linear ticket ID following the convention {type}/{ticket-id}-short-description

Git Branch Create

Resolve a ticket branch name following the project's naming convention.

In parallel workflows, branch creation should happen through a dedicated worktree (via git-worktree-prepare), not by checking out directly in the current tree.

Branch Format

{type}/{ticket-id}-short-description

Type Prefixes

Type	Use Case
`feat`	New features or functionality
`fix`	Bug fixes
`refactor`	Code refactoring without functional changes
`docs`	Documentation changes
`test`	Adding or updating tests
`chore`	Maintenance tasks, dependencies, tooling
`perf`	Performance improvements

Steps

Determine the type from the ticket:
- Look at the ticket type/label in Linear
- If unclear, ask the user
Extract ticket ID:
- Format: STU-XX (or similar project prefix)
- Keep the full ID including prefix
Create short description:
- Use 2-4 words from the ticket title
- Lowercase, hyphen-separated
- No special characters
- Max 30 characters
Construct branch name:
```
{type}/{ticket-id}-{short-description}
```
Do not check out in the current tree:
- Do not run git checkout -b in the active workspace
- Return the constructed branch name to the caller
Handoff to worktree flow:
- The caller should run git-worktree-prepare with the constructed branch name
- Let that skill create/reuse the actual branch checkout

Examples

Ticket	Title	Branch Name
STU-15	Add user authentication	`feat/STU-15-user-authentication`
STU-23	Fix login timeout issue	`fix/STU-23-login-timeout`
STU-42	Refactor API error handling	`refactor/STU-42-api-error-handling`

Validation

Before returning the branch name:

Fetch latest refs: git fetch --all --prune
Check branch candidates: git branch -a | grep {ticket-id}

If a branch for this ticket already exists, inform the user and ask whether to:

Reuse the existing branch name
Create a new branch with a different suffix

Output

Return:

Branch: <branch-name>
Branch state: <new|existing>

Más de este repositorio

mismo repositorio

git-find-ticket-branch

f4irline/bbqparty-ai

Find a git branch by Linear ticket ID prefix (e.g., STU-15)

2026-02-204

git-worktree-prepare

f4irline/bbqparty-ai

Create or reuse a dedicated git worktree for a branch using a deterministic path layout

2026-02-204

progress-doc

f4irline/bbqparty-ai

Create and maintain implementation progress documentation for a feature branch

2026-02-204

git-worktree-find

f4irline/bbqparty-ai

Find the worktree path for a branch and create/reuse it when missing

2026-02-194

git-push-remote

f4irline/bbqparty-ai

Push the current branch to the remote repository with upstream tracking

2026-02-154

github-pr-feedback

f4irline/bbqparty-ai

Fetch unresolved review threads and PR comments for the pull request tied to the resolved target branch

2026-02-074

Git Branch Create

Resolve a ticket branch name following the project's naming convention.

In parallel workflows, branch creation should happen through a dedicated worktree (via git-worktree-prepare), not by checking out directly in the current tree.

Branch Format

{type}/{ticket-id}-short-description

Type Prefixes

Type

Use Case

feat

New features or functionality

fix

Bug fixes

refactor

Code refactoring without functional changes

docs

Documentation changes

test

Adding or updating tests

chore

Maintenance tasks, dependencies, tooling

perf

Performance improvements

Steps

Determine the type from the ticket:

Look at the ticket type/label in Linear
If unclear, ask the user

Extract ticket ID:

Format: STU-XX (or similar project prefix)
Keep the full ID including prefix

Create short description:

Use 2-4 words from the ticket title
Lowercase, hyphen-separated
No special characters
Max 30 characters

Construct branch name:

{type}/{ticket-id}-{short-description}

Do not check out in the current tree:

Do not run git checkout -b in the active workspace
Return the constructed branch name to the caller

Handoff to worktree flow:

The caller should run git-worktree-prepare with the constructed branch name
Let that skill create/reuse the actual branch checkout

Examples

Ticket

Title

Branch Name

STU-15

Add user authentication

feat/STU-15-user-authentication

STU-23

Fix login timeout issue

fix/STU-23-login-timeout

STU-42

Refactor API error handling

refactor/STU-42-api-error-handling

Validation

Before returning the branch name:

Fetch latest refs: git fetch --all --prune

Check branch candidates: git branch -a | grep {ticket-id}

If a branch for this ticket already exists, inform the user and ask whether to:

Reuse the existing branch name

Create a new branch with a different suffix

Output

Return:

Branch: <branch-name> Branch state: <new|existing>