Skill

generate-branch-name

From tac

Generates semantic Git branch names from GitHub issue context using feat/fix/chore-{number}-{8-char-id}-{kebab-slug} convention for ADW workflows. Use before starting issue work.

Git

npx claudepluginhub melodic-software/claude-code-plugins --plugin tac

Tool Access

This skill is limited to using the following tools:

ReadBash

Preview

Generate a semantic Git branch name following the convention.

SKILL.md

Similar Skills

git-branch-naming

Enforces Git branch naming conventions with type prefixes (feat, fix, chore), issue linking, and kebab-case formatting. Use for creating branches, validating names, or setting repository standards.

4 tools

git-plugin

create-branch

680

Creates git branches following Sentry naming conventions (<prefix>/<type>/<short-description>). Infers type from git diff/status/arguments, selects base branch, avoids collisions.

sentry-skills

create-branch

37.1k

Creates git branches following Sentry naming conventions (<username>/<type>/<description>) from arguments, local diffs, or user input. Classifies types like feat/fix/ref/chore. Uses gh CLI for username prefix.

antigravity-awesome-skills

Stats

Parent Repo Stars63

Parent Repo Forks9

Last CommitMar 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Branch Name Generation

Generate a semantic Git branch name following the convention.

Branch Naming Convention

{type}-{issue_number}-{short_id}-{slug}

Components:

type: feat, fix, chore (from issue classification)

issue_number: GitHub issue number

short_id: 8-character identifier (ADW ID if provided)

slug: Kebab-case summary of issue (max 30 chars)

Examples

feat-123-a1b2c3d4-add-user-auth fix-456-e5f6g7h8-login-double-submit chore-789-i9j0k1l2-update-dependencies

Rules

Use lowercase letters, numbers, and hyphens only

No spaces or special characters in slug

Slug should be descriptive but concise (max 30 chars)

Response should be ONLY the branch name, nothing else

Arguments

$1: Issue type (feat, fix, chore)

$2: Short ID (8 characters, or generate one)

$ARGUMENTS: Issue title or description

Generation Process

Take the issue type from $1

Extract issue number if present in arguments

Use provided short ID from $2 or generate 8 random hex chars

Create slug from issue description:

Convert to lowercase
Replace spaces with hyphens
Remove special characters
Truncate to 30 characters
Remove trailing hyphens

Issue Context

Type: $1 ID: $2 Issue: $ARGUMENTS

Branch Name Generation

Generate a semantic Git branch name following the convention.

Branch Naming Convention

{type}-{issue_number}-{short_id}-{slug}

Components:

type: feat, fix, chore (from issue classification)
issue_number: GitHub issue number
short_id: 8-character identifier (ADW ID if provided)
slug: Kebab-case summary of issue (max 30 chars)

Examples

feat-123-a1b2c3d4-add-user-auth
fix-456-e5f6g7h8-login-double-submit
chore-789-i9j0k1l2-update-dependencies

Rules

Use lowercase letters, numbers, and hyphens only
No spaces or special characters in slug
Slug should be descriptive but concise (max 30 chars)
Response should be ONLY the branch name, nothing else

Arguments

$1: Issue type (feat, fix, chore)
$2: Short ID (8 characters, or generate one)
$ARGUMENTS: Issue title or description

Generation Process

Take the issue type from $1
Extract issue number if present in arguments
Use provided short ID from $2 or generate 8 random hex chars
Create slug from issue description:
- Convert to lowercase
- Replace spaces with hyphens
- Remove special characters
- Truncate to 30 characters
- Remove trailing hyphens

Issue Context

Type: $1 ID: $2 Issue: $ARGUMENTS