git-branch-practices

Valid git branch names must follow a <type>/<description> format using approved prefixes such as feature/, bugfix/, hotfix/, release/, refactor/, docs/, test/, or chore/. Descriptions must be lowercase, hyphenated, and include ticket IDs when available.

You can enforce consistent git branch naming in CI by validating branches against approved prefixes and a <type>/<description> format. This skill provides rules and workflow guidance that integrate with hooks or CI pipelines to reject non-compliant names automatically.

Use the feature/ prefix for new functionality and the hotfix/ prefix for urgent production fixes. Both require a lowercase, hyphenated description following the prefix, and should include an optional ticket ID to maintain clear version-control history.

Using hyphens and ticket IDs in git branch names prevents ambiguous references and links work directly to project tracking. Hyphens ensure readable lowercase descriptions, while ticket IDs provide traceability for collaboration and faster code reviews.

Yes, this branch naming guidance supports integration across various Git workflows. It provides standard prefixes and format rules that apply universally, helping teams standardize branch naming conventions without overhauling their existing version-control processes.

To validate a git branch name, check it against the required <type>/<description> format and approved prefixes like chore/ or docs/. Ensure the description uses lowercase words separated by hyphens, avoids vague terms, and includes a ticket ID if available.