speckit-git-validate

Validate Git branch names against feature-branch naming conventions and spec directories.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/vZulin/overlay-clock-timer --skill speckit-git-validate-vzulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/vZulin/overlay-clock-timer/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/vZulin/overlay-clock-timer --skill speckit-git-validate-vzulin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that the active Git branch follows the expected feature-branch naming conventions to keep repositories tidy and branch workflows predictable.

Core Features & Use Cases

  • Enforces naming patterns for feature work using sequential prefixes like 001-feature-name and timestamp prefixes like 20260319-143022-feature-name, and checks for the existence of a matching spec directory under specs/.
  • Supports graceful degradation when Git is unavailable by allowing a SPECIFY_FEATURE fallback and clear warnings.

Quick Start

Provide the current Git branch name and verify it matches the allowed patterns.

Frequently Asked Questions about speckit-git-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Git branch naming conventions in CI automation?

To validate feature-branch naming rules, the Skill checks the current Git branch name against predefined patterns like 001-feature-name or timestamp formats like YYYYMMDD-HHMMSS-feature-name. It also verifies a matching spec directory exists under specs/ within the spec-kit project structure.

What Git branch naming patterns are supported for spec-kit projects?

Spec-kit projects support branch naming patterns using sequential prefixes (001-feature-name) and timestamp prefixes (YYYYMMDD-HHMMSS-feature-name). The Skill validates the active branch against these patterns and confirms a matching specs/ directory exists.

Can I check for a matching spec directory when validating a Git feature branch?

Yes, you can check for a matching spec directory during branch validation. The Skill requires compatibility with the spec-kit project structure and reports whether a corresponding specs/ directory exists after validating the branch naming convention.

Does the Git branch validation tool work when Git is unavailable?

When Git is unavailable, branch validation supports graceful degradation by allowing a SPECIFY_FEATURE fallback. This provides clear warnings instead of failing the process, allowing development workflows to continue with manual specification.

What are the limitations of enforcing branch naming rules with sequential prefixes?

Limitations include strict compatibility with the spec-kit project structure. The validation only recognizes sequential prefixes (001-feature-name) or timestamp prefixes (YYYYMMDD-HHMMSS-feature-name), so non-standard branch names will fail and missing specs/ directories are reported as non-matching.

Why does my feature branch validation fail to find a matching spec directory?

Validation fails to find a matching spec directory when the branch name follows the correct naming convention but the expected directory under specs/ does not exist. The Skill reports this mismatch to maintain predictable branch workflows and repository tidiness.