branch-naming

Name: branch-naming
Availability: InStock
Author: notque

Generate Git branch names from conventional commit messages with kebab-case formatting.

415|44|Updated Mar 18, 2026

Search Tags:#automation #git #validation #kebab-case #conventional-commits #branch-naming

Ready to run

npx skills add https://github.com/notque/claude-code-toolkit --skill branch-naming-notque

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: branch-naming
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/branch-naming
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill branch-naming-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Generating consistent, descriptive Git branch names from conventional commits or plain descriptions to improve collaboration, traceability, and automation reliability.

Core Features & Use Cases

Conventional commit type to prefix mapping (feat -> feature/, fix -> fix/, docs/ -> docs/ etc.)
Sanitization to kebab-case with a 50-character total length limit
Duplicate detection with alternative suggestions and repository config overrides
Validation against naming conventions (prefix, length, allowed characters)
Real-world use cases: turning commits into ready-to-use branches for features, fixes, and docs

Quick Start

Provide a conventional commit message or plain description and the skill will generate a compliant branch name.

Frequently Asked Questions about branch-naming

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

FAQPage Schema

How do I generate a Git branch name from a conventional commit message?▼

Generate a Git branch name from a conventional commit by mapping standard commit types like feat or fix to prefixes, sanitizing the subject to kebab-case, and enforcing a 50-character limit. The output is a structured payload ready for automated use.

What is the best way to enforce kebab-case and length limits for Git branch names?▼

Enforce kebab-case and length limits for Git branch names by validating against allowed characters and applying a 50-character total length constraint. This sanitization ensures branch names remain consistent, descriptive, and compliant with repository naming conventions.

Can I use conventional commit type mappings to create branch prefixes automatically?▼

Map conventional commit types to branch prefixes automatically by translating standard commits like feat to feature/ and docs to docs/. This automated prefixing improves collaboration, traceability, and automation reliability across your repository.

How do I handle duplicate Git branch names when automating branch creation?▼

Handle duplicate Git branch names by detecting existing matches and suggesting alternative branch names automatically. The generated payload includes optional duplicate suggestions and supports repository config overrides to resolve naming conflicts without manual intervention.

Does Git branch naming validation work with plain text descriptions instead of commit messages?▼

Git branch naming validation works with plain text descriptions by applying the same kebab-case sanitization, prefix mapping, and 50-character length enforcement used for conventional commit messages to produce a valid, structured branch name payload.