speckit-git-validate

To validate Git branch naming conventions, this Skill checks the active branch against sequential patterns like ^[0-9]{3,}- and timestamp patterns like ^[0-9]{8}-[0-9]{6}-. It reports whether the branch matches feature-branch naming rules and locates related spec directories under specs/.

When Git is unavailable or the directory is not a Git repository, branch name validation uses graceful degradation. It falls back to environment variables or skips validation with a warning message, ensuring the workflow continues without hard failures.

Yes, speckit-git-validate is designed for spec-kit projects containing a .specify/ directory. It confirms whether a corresponding spec directory exists under specs/ when a feature branch is active, providing actionable messages for non-feature branches.

To check if a Git feature branch has a matching spec directory, run the validation Skill against the active branch name. It verifies the branch matches sequential or timestamp naming patterns, then confirms a corresponding spec directory exists under specs/.

Spec-kit validation supports two feature-branch naming patterns: sequential prefixes matching ^[0-9]{3,}- (three or more digits) and timestamp prefixes matching ^[0-9]{8}-[0-9]{6}- (YYYYMMDD-HHMMSS format). Branches matching either pattern are validated as feature branches.

Branch name validation reports a non-feature branch warning when the active Git branch does not match either the sequential ^[0-9]{3,}- or timestamp ^[0-9]{8}-[0-9]{6}- patterns. The Skill provides actionable messages indicating the branch does not follow feature-branch naming conventions.