speckit-git-validate

Git branch validation for SpecKit confirms your current branch matches sequential or timestamp feature naming patterns and checks that a corresponding specs/<prefix>-* directory exists. This prevents mismatches between branch names and spec directories during review workflows.

If Git is unavailable or you are outside a repository, SpecKit branch validation falls back to reading the SPECIFY_FEATURE environment variable. It uses this fallback branch name to enforce prefix-matching rules against the expected specs/<prefix>-* paths.

Branch prefix matching extracts a prefix from your current Git branch name and verifies that a matching spec directory exists under the specs/ path. It enforces naming rules against specs/<prefix>-* paths to ensure structural alignment for validation workflows.

Git is required for normal SpecKit directory cross-checks inside a repository, but the validation gracefully falls back to the SPECIFY_FEATURE environment variable if Git is unavailable. This allows branch and spec directory validation to proceed outside a Git context.

SpecKit validation fails when the Git branch name prefix does not match the corresponding specs/ directory name, preventing broken links in review workflows. It enforces strict prefix-matching rules against specs/<prefix>-* paths for both sequential and timestamp-based branches.