speckit-git-validate

To validate Git feature branch naming, extract the current branch name, match it against sequential numeric or timestamp-based regex patterns, and confirm the corresponding specs/ prefix directory exists. This prevents broken workflows caused by misnamed feature branches.

Enforcing CI guardrails for branch naming involves checking Git repository availability, extracting the branch name, applying regex pattern matching for supported prefixes, and verifying the matching specs directory exists to ensure workflow consistency across feature development.

Git branch validation handles repository unavailability gracefully by skipping cleanly and optionally validating the SPECIFY_FEATURE environment variable as a fallback, ensuring workflow consistency is maintained even outside a Git context.

Checking feature branch prefix correspondence involves extracting the branch name, applying regex patterns to identify the prefix, and verifying that a matching specs/<prefix>-* directory exists locally to maintain workflow consistency during development.

Feature branch validation supports two primary regex pattern formats: sequential numeric prefixes and timestamp-based prefixes. Both patterns are matched against the current branch name to extract the prefix used for spec directory lookup.

Feature branch validation fails when the specs directory is missing because the Skill enforces strict correspondence between the extracted branch prefix and the local specs/<prefix>-* directory, preventing wasted time on disconnected branches.