speckit-git-validate

To validate Git branch names, the Skill checks the active branch against sequential and timestamp prefixes to confirm compliance with team conventions. It verifies the branch name pattern matches the required format and reports any naming mismatches during development.

To check for a matching spec directory, the Skill reads the branch prefix and searches for a corresponding specs/<prefix>-* directory within the spec-kit project structure. It reports success if the directory exists or issues a warning if the specification files are missing.

Yes, branch naming validation works in CI checks without Git by falling back to the SPECIFY_FEATURE environment variable. When Git is unavailable, the Skill reads this variable to determine the feature prefix and validate the expected spec directory structure.

For spec-kit project structure validation, the Skill supports sequential naming patterns like 001-feature and timestamp patterns like 20260319-143022-feature. It performs pattern matching on these prefixes to ensure branches align with the repository's specification directories.

Feature branch validation reports a missing specification directory warning when the branch prefix does not match any existing specs/<prefix>-* directory in the .specify path. This indicates a naming mismatch between the Git branch and the actual specification files created.