git-branch-naming-setup

Git Branch Naming Setup

Interactive wizard to create or update .claude-plugin/git-branch-naming.json for your project.

What this command does

1. Shows current configuration (if exists)
2. Asks configuration questions via dialog
3. Creates/updates .claude/git-branch-naming.json
4. Optionally installs .githooks/pre-push hook

Setup Steps

Step 1: Check existing config

Read .claude-plugin/git-branch-naming.json if it exists (show current values as defaults). Otherwise use defaults from ${CLAUDE_PLUGIN_ROOT}/templates/git-branch-naming.json.

Step 2: Ask configuration questions

Use AskUserQuestion to collect:

Question 1 — Allowed prefixes (multiSelect):

• feature, bugfix, hotfix, release, docs, test, chore, refactor ← all selected by default
• Allow "Other" to add custom prefixes

Question 2 — Ticket number requirement:

• No ticket required (default)
• JIRA format: [A-Z]+-\d+ (e.g., PROJ-123)
• GitHub issue: #\d+ (e.g., #42)
• Custom pattern (ask for regex)

Question 3 — Max branch name length:

• 60 characters (default)
• 80 characters
• 100 characters
• No limit

Question 4 — Protected branches (multiSelect):

• main, master, develop ← all selected by default

Question 5 — Enforcement level (applies to ALL rules):

• Ask (warn, let user decide) ← default
• Deny (block the command)
• Per-rule (ask for each of: invalid name, protected branch, content mismatch)

Question 6 — Content mismatch detection:

• Enable (warn when branch type doesn't match staged/pushed files) ← default
• Disable

Question 7 — Open PR check (what happens when branch has an open PR by another author):

• Ask (warn, let user decide) ← default
• Deny (block the command)
• Off (skip check entirely)

Question 8 — Install pre-push git hook?:

• Yes, install to .githooks/pre-push (requires git config core.hooksPath .githooks)
• No

Step 3: Write config file

Create .claude-plugin/ directory if needed, then write .claude-plugin/git-branch-naming.json: