speckit-git-validate

To validate a Git branch name against feature-branch naming conventions, run the validation command to check the current branch against supported sequential and timestamp patterns. It also verifies a corresponding spec directory exists under specs/ for the detected prefix.

If Git is unavailable or the current directory is not a repository, branch name validation applies graceful degradation by falling back to the SPECIFY_FEATURE variable or skipping the validation entirely to avoid blocking your workflow.

Yes, feature-branch naming validation checks for corresponding spec directories. After identifying a matching branch name prefix, it verifies that the expected spec directory exists under the specs/ folder to maintain project consistency.

Feature-branch validation supports both sequential and timestamp naming patterns. It identifies whether the current Git branch name matches these supported feature naming conventions before verifying the associated spec directory structure.

You need to validate feature-branch naming conventions when starting work on a new feature. This ensures naming consistency across your team and correctly maps the active branch to its corresponding specification directory under specs/.