speckit-git-validate

Run the branch validation to compare the current branch from git rev-parse --abbrev-ref HEAD against the sequential pattern ^[0-9]{3}- or the timestamp pattern ^[0-9]{8}-[0-9]{6}-. It reports whether the branch is a valid feature branch.

Spec-kit feature branches use either a sequential numeric prefix like 001-feature-name or 1000-big-feature, or a timestamp prefix like 20260319-143022-feature-name. Branches not matching either pattern are flagged as non-feature branches.

Yes, it degrades gracefully. If Git is unavailable or the directory is not a repository, it checks the SPECIFY_FEATURE environment variable as a fallback, and if that is unset it skips validation with a warning instead of failing.

After confirming a valid feature branch, the check looks for a matching directory under specs/ using the branch's numeric or timestamp prefix. A missing directory means the spec for that feature has not been created yet, so the warning prompts you to set it up.

It only checks naming patterns and spec directory existence; it does not verify branch contents, commit history, or spec file correctness. It also requires the spec-kit project structure with a .specify/ directory to be meaningful.