speckit-git-validate

You can validate feature-branch naming conventions by running the Skill to check the current Git branch name against sequential or timestamp patterns. It reports whether the branch matches and if a corresponding spec directory exists under specs/.

The expected naming convention requires branch names to use sequential prefixes like 001-feature-name or timestamp prefixes like 20260319-143022-feature-name. This ensures consistency across teams and pipelines in Git repositories.

Yes, you can enforce branch name validation without Git by using the SPECIFY_FEATURE fallback. The Skill gracefully handles cases where Git is not available or the current directory is not a Git repository.

Yes, the validator checks whether a matching spec directory exists under specs/. It provides execution feedback that includes the current branch status and confirms if the corresponding spec directory is present.

If you run the validator outside of a Git repository, it gracefully degrades instead of throwing an error. It handles the missing repository context smoothly and can use the SPECIFY_FEATURE fallback to continue validation.

Teams use timestamp-based prefixes like 20260319-143022-feature-name to ensure chronological sorting and prevent naming collisions. Validating these patterns maintains consistency and traceability across development pipelines.