speckit-git-validate

Git branch name validation checks the current branch against sequential (e.g., 001-feature-name) or timestamp (e.g., 20260319-143022-feature-name) patterns. It also verifies a corresponding specs/<prefix>-* directory exists to ensure automated tooling reliably maps to feature work.

The spec-kit branch naming convention requires a sequential prefix like 001- or a timestamp prefix like 20260319-143022-. This ensures feature branches consistently map to their corresponding specs/<prefix>-* directories and pass CI checks.

When Git is unavailable, branch validation falls back to the SPECIFY_FEATURE environment variable. It skips validation with a clear warning, making it suitable for local checks, pre-commit hooks, and CI pipelines.

To check if a spec directory exists, run the validation in your project root. It verifies that a matching specs/<prefix>-* directory corresponds to your branch prefix and reports any missing spec directories.

Feature branches fail CI checks due to mismatched specifications when the branch name does not follow sequential or timestamp patterns, or when the corresponding specs/<prefix>-* directory is missing from the repository.

speckit-git-validate applies to repositories using the spec-kit project structure with a .specify directory. It relies on this structure to verify the corresponding specs/<prefix>-* directory exists for feature work.