speckit-git-validate

Validating Git branch naming conventions in CI pipelines checks the current branch against predefined patterns like sequential prefixes or timestamps. This skill detects Git presence, verifies feature branch formats, and checks for spec directories under specs/ when applicable.

Supported feature branch naming patterns include sequential prefixes like 001-feature and timestamp-based names like 20260319-143022-feature-name. These patterns ensure consistent ordering in CI dashboards and support time-based traceability for development workflows.

Branch name validation gracefully degrades in non-Git environments by issuing warnings instead of failing. When Git is unavailable or specs directories are missing, the validation detects the absence and proceeds without blocking the development workflow.

Enforcing consistent feature branch naming with sequential prefixes involves validating branch names like 001-feature or 042-bugfix against established patterns. This discipline accelerates review workflows and ensures reliable automation by preventing inconsistent naming across teams.

Checking for spec directories when validating a feature branch is supported under the specs/ path. When on a feature branch, the validation verifies the existence of corresponding specs, ensuring documentation aligns with branch naming conventions.

Validating timestamp-based Git branch names like 20260319-143022-feature-name supports time-based traceability across development workflows. This pattern allows teams to track when branches were created, improving historical context and CI validation reliability.