branch-naming

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.

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.

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.

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.

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.