speckit-git-validate

To enforce Git feature-branch naming automatically, you need a validation tool that checks the active branch name against sequential or timestamp-based patterns. This ensures branch names conform to predefined rules before development continues.

If Git is unavailable or the directory is not a repository, the branch validation process uses graceful degradation. It checks for a SPECIFY_FEATURE environment variable fallback to maintain workflow consistency without failing the operation.

Sequential and timestamp-based feature branch patterns are naming conventions that embed chronological data into the branch name. Validating these patterns ensures development traceability and maintains historical consistency across Git workflows.

To validate your current Git branch name, run the validation command to inspect the repository state. It confirms the active branch adheres to feature-branch rules and reports if a spec directory or fallback is available.

A spec directory is not strictly required for Git branch validation to work. The validation process reports if a spec directory or fallback is available, relying on the SPECIFY_FEATURE environment variable if the directory is missing.

Feature branch validation fails outside a Git repository because the process requires Git to inspect active branch names. Without Git, it triggers graceful degradation and attempts to use the SPECIFY_FEATURE environment variable instead.