speckit-git-validate

To validate a Git branch name against a spec directory, you can run a check that extracts the current branch name, matches it against sequential or timestamp naming conventions, and confirms a corresponding specs/<prefix>-* directory exists. This ensures branch-driven feature validation consistency.

Feature branch validation supports sequential naming patterns (e.g., 001-feature-name) and timestamp-based naming patterns (e.g., 20260319-143022-feature-name). These conventions ensure branches map correctly to their corresponding specs directories.

Yes, you can check branch naming conventions without Git by using the SPECIFY_FEATURE environment variable as a fallback. This allows CI workflows to validate the expected prefix and verify the matching spec directory even when Git repository detection is unavailable.

CI pipelines break because branch-driven feature validation relies on consistent specs/<prefix>-* mappings. If a branch name does not follow the expected sequential or timestamp naming conventions, the matching spec directory cannot be found, causing the workflow to fail.

The best way to enforce repository hygiene is to apply CI checks that validate branch names against expected regex patterns and cross-check for a matching spec directory. This prevents workflow breakages by ensuring consistent feature branch naming and spec mapping.

Yes, you need a matching specs directory for every Git feature branch. The validation process computes a prefix from the branch name and checks for the presence of a corresponding specs/<prefix>-* directory to ensure proper feature validation.