speckit-git-validate

Validate Git branch naming conventions by reading the current branch name and matching it against expected numeric and timestamp regex patterns to ensure sequential feature branch compliance. The Skill enforces this by checking branch-to-spec mapping during CI or local workflows.

When Git is unavailable or the directory is not a Git repository, branch validation falls back to the SPECIFY_FEATURE environment variable. This graceful degradation ensures workflow enforcement continues without direct Git access.

Yes, you can enforce spec directory presence by deriving the branch prefix from the Git branch name and verifying the matching spec directory exists under the expected specs/ path. This correlation prevents broken Spec-to-branch workflows.

Feature branch detection uses numeric and timestamp regex patterns to match sequential or timestamped branch names. The validation process checks the extracted branch name against these patterns to confirm naming compliance.

Yes, spec-kit branch validation works outside Git repositories by supporting the SPECIFY_FEATURE fallback environment variable. This allows filesystem validation and branch-to-spec mapping to proceed even when Git is not present.

CI checks fail on invalid feature branch names because the branch does not match the expected sequential or timestamped naming patterns, or the corresponding spec directory is missing under the specs/ path. Validation enforces branch-to-spec correlation.