speckit-git-validate

Validate Git branch names against feature-branch naming conventions.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill speckit-git-validate-chaimt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/speckit-git-validate
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill speckit-git-validate-chaimt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that the active Git branch name conforms to predefined feature-branch naming conventions.

Core Features & Use Cases

  • Branch-name pattern checks: sequential prefixes like 001-feature-name or 042-fix-bug and timestamp prefixes like 20260319-143022-feature-name.
  • Spec directory verification: checks for corresponding specs/ directory under specs/ that matches the branch prefix.
  • Graceful fallback: when Git is unavailable or not in a repo, uses SPECIFY_FEATURE environment variable as a fallback and provides warnings instead of failing.

Quick Start

Run the speckit-git-validate skill in your repository to verify the current branch matches the supported patterns and locate the corresponding specs directory.

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 for feature work?

You can validate Git feature-branch naming by checking the active branch against predefined sequential or timestamp prefix patterns. The validation reports pattern conformance and whether a matching spec directory exists under specs/.

What Git branch naming patterns are supported for spec-driven workflows?

Supported Git branch naming patterns include sequential numeric prefixes like 001-feature-name or 042-fix-bug and timestamp prefixes like 20260319-143022-feature-name. These patterns determine feature work and locate corresponding spec directories.

How do I check if a Git branch has a corresponding spec directory?

To check for a corresponding spec directory, the validation process matches the active Git branch prefix against directories under specs/. This confirms whether the required spec folder exists for the current feature work.

Can I validate branch names without an active Git repository?

Branch name validation can proceed without an active Git repository by using the SPECIFY_FEATURE environment variable as a fallback. The validation provides warnings instead of failing when Git is unavailable or not in a repo context.

What should I do if my Git branch name doesn't match feature-branch conventions?

If your Git branch name doesn't match feature-branch conventions, the validation reports the pattern mismatch. You should rename the branch using a sequential prefix like 001-feature-name or a timestamp prefix, and ensure a matching spec directory exists under specs/.

Does Git branch validation work with both sequential and timestamp naming schemes?

Git branch validation works with both sequential and timestamp naming schemes. It enforces pattern checks for sequential prefixes like 001-feature-name and timestamp prefixes like 20260319-143022-feature-name, reporting conformance and spec directory existence.