speckit-git-validate

To validate Git branch naming conventions, you can use this Skill to check branch names against sequential or timestamp-based patterns, ensuring project consistency and traceability to specific specifications.

Yes, you can check if a Git branch has a corresponding specification directory by running this Skill, which automatically verifies the existence of linked documentation folders within standard project structures.

Yes, Git branch validation requires access to Git CLI commands and a standard project structure to perform both branch naming checks and the verification of corresponding specification directories.

Supported naming patterns for enforcing Git branch consistency include sequential and timestamp-based formats, which prevent repository clutter by ensuring every feature branch is traceable to a specific specification.

You should enforce branch naming conventions in a Git workflow when developers create new feature branches, ensuring the branch name is correctly formatted and associated design or requirement documentation exists in the specs folder.