speckit-git-validate

Git branch naming conventions are validated by checking the current branch name against sequential three-or-more digit prefixes or timestamp-based prefixes, ensuring compliance with team workflows. The validation also verifies a corresponding spec directory exists under specs/.

Branch validation gracefully degrades when Git is unavailable or the directory is not a Git workspace, providing clear warnings instead of failing. An optional SPECIFY_FEATURE fallback can be used to handle these edge cases smoothly.

Feature branch name pattern matching works by enforcing strict adherence to either a sequential three-or-more digit prefix or a timestamp-based prefix format. This standardization reduces confusion and aligns local branches with team conventions.

Branch validation does check for a corresponding spec directory under specs/ to ensure documentation aligns with the branch. It provides clear messaging indicating success, warnings, or missing spec directories after the check.

You can use this branch validation tool without configuring external dependencies, as it operates with zero required dependencies. It functions directly within local development environments to enforce feature branch naming rules.

Enforcing feature branch naming conventions in DevOps workflows reduces confusion in collaborative environments by standardizing names. It ensures sequential or timestamp prefixes are used consistently and that matching spec directories are maintained.