speckit-git-validate

Feature branch naming validation checks the current Git branch against expected sequential or timestamp-based patterns. It outputs pass/fail messages to enforce naming conventions without performing destructive actions during your feature development workflow.

Spec directory alignment ensures a corresponding spec directory exists under the expected specs/ prefix for your branch. It prevents broken or inconsistent feature branch naming by automatically checking the current branch against the conventions your spec system expects.

You enforce CI guardrails by applying regex-based pattern checks during feature development workflows. This validates branch naming and verifies that a corresponding spec directory exists for the branch prefix before allowing commits to proceed.

When Git is unavailable, branch naming validation safely skips by checking an override from the SPECIFY_FEATURE environment variable. This graceful fallback ensures validation can still function in restricted environments without failing the workflow.

The best way to automate spec-driven directory validation is running regex-based pattern checks at commit time. This verifies both the feature branch name and its corresponding specs directory existence, outputting clear pass/fail/warning messages for sequential or timestamped branches.