speckit-git-validate

To validate a Git branch name against feature-branch conventions, run this skill in your repository. It checks the current branch against sequential (000-) or timestamp (YYYYMMDD-HHMMSS-) prefixes and prints clear results with guidance for next steps.

Supported Git feature-branch naming patterns include sequential formats with a 000- prefix and timestamp formats with a YYYYMMDD-HHMMSS- prefix. The skill verifies your current branch matches these established conventions to prevent misrouted changes.

Yes, you can check for a corresponding spec directory under specs/. After validating the branch prefix, the skill performs spec discovery to verify the existence of a matching specs path for the detected sequential or timestamp prefix.

If Git is unavailable when checking feature-branch naming conventions, the skill gracefully degrades by reading the SPECIFY_FEATURE environment variable as a fallback. If that is missing, it outputs a warning instead of failing.

You need to enforce feature-branch naming patterns to prevent misnamed work and misrouted changes in your repository. Validating branch names against sequential or timestamp conventions ensures consistency and locates matching spec paths.