speckit-branch-convention-configure

You can configure spec-kit branch naming conventions by selecting presets like gitflow, ticket, date, or custom patterns. The Skill validates these patterns to ensure generated names conform to allowed tokens.

Yes, you can use a custom branch pattern instead of the default gitflow convention. The Skill validates custom patterns to ensure generated branch and folder names conform to allowed tokens and formatting rules.

Spec-kit branch and folder naming rules are stored in the .specify/branch-convention.yml file. This configuration file persists your selected preset or custom patterns for the current project.

Yes, the branch convention configuration validates existing git branches. It assists in auditing existing branches for conformance to the configured patterns and offers quick remediation guidance for non-compliant names.

Custom branch naming patterns in spec-kit are limited by validation rules that ensure generated names conform to allowed tokens and formatting. Patterns failing these validation checks will not be accepted into the configuration file.