speckit-git-validate

Feature-branch naming validates that your active Git branch matches established patterns like a 3+ digit prefix or a timestamp prefix. This prevents inconsistent branch tracking and maintains consistent review workflows across your repository.

Valid Spec-kit branch name patterns include a 3+ digit prefix like 001-feature and a timestamp prefix formatted as YYYYMMDD-HHMMSS-feature. The validation maps these prefixes to corresponding entries under the specs/ directory.

Branch name validation handles Git unavailability through graceful degradation. It uses a provided SPECIFY_FEATURE fallback to continue processing, otherwise it skips validation and prints a warning message to alert the user.

To verify a spec directory exists, run the validation on your current Git branch. It checks the branch name prefix and maps it to a corresponding specs/ entry, confirming alignment with your Spec-kit structure and printing status messages.

Branch naming validation is needed to prevent inconsistent branch tracking and review workflows. It ensures every feature branch follows established conventions and maps correctly to its corresponding spec directory for accurate documentation alignment.

You can use a fallback when Git cannot detect the current branch by providing the SPECIFY_FEATURE variable. This allows the validation logic to proceed gracefully instead of skipping the entire workflow with a warning.