speckit-git-validate

Git branch naming conventions are validated by checking the current branch name against sequential and timestamp formats to ensure predictable feature tracking and spec discovery. The skill matches branch prefixes to expected directory structures for workflow automation.

Feature branch validation supports sequential naming formats like 001-feature-name and timestamp-based formats such as 20260319-143022-feature-name. These patterns ensure branch prefixes map predictably to corresponding spec directories.

Spec directory existence is checked by verifying that a corresponding specs/<prefix>-* folder matches the detected Git branch prefix. This filesystem cross-check confirms that required documentation is present for the active feature branch.

Feature branch validation without Git relies on a graceful fallback to the SPECIFY_FEATURE environment value. When Git is unavailable, the skill validates the feature name from this environment variable instead of failing the workflow.

CI pipelines need branch naming validation and spec directory checks to prevent broken or inconsistent Git feature branch naming from disrupting downstream spec discovery. Enforcing these CI guardrails maintains predictable repository workflows and automation.

Feature branch validation checks for the existence of a corresponding specs directory based on the branch prefix. While the skill detects this directory, ensuring your repository workflow creates the matching specs/<prefix>-* folder beforehand guarantees successful validation.