speckit-git-validate

You can validate Git branch naming by checking the current branch name against the project's feature-branch rules, ensuring consistency and preventing drift in CI workflows across sequential and timestamp-based prefixes.

Branch naming validation works by checking for a corresponding spec path under the specs/ directory for the current branch prefix. It matches feature prefixes or timestamps to locate the relevant spec.

If Git is unavailable or you are outside a repository, branch validation handles the situation gracefully and provides an optional fallback using the SPECIFY_FEATURE environment variable to specify the feature context.

Yes, a specs directory structure is required to enforce feature-branch naming rules. The validation process relies on the specs/ directory to locate the corresponding spec for the current branch prefix.

The best way to prevent branch naming drift is to validate the current Git branch name against the project's feature-branch naming rules before integration. This checks for spec path existence under specs/ for feature prefixes or timestamps.