skills.rest
sdk451
sdk451COMMUNITY
Explore all skills by this author →
GitHub

speckit-git-validate

Validate Git branch names against sequential or timestamped patterns and matching spec directories.

Updated Apr 25, 2026
Search Tags:#git#validation#patterns#specs#branch-name
One-click install
npx skills add https://github.com/sdk451/claude-gdrive --skill speckit-git-validate-sdk451
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/sdk451/claude-gdrive/tree/main/.cursor/skills/speckit-git-validate
Command: npx skills add https://github.com/sdk451/claude-gdrive --skill speckit-git-validate-sdk451

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that the current Git branch name conforms to predefined feature-naming patterns, helping teams avoid misnamed branches and related workflow issues.

Core Features & Use Cases

  • Validates branch-name against sequential patterns like 001-feature-name and timestamp-based patterns like 20260319-143022-feature-name.
  • Checks for a corresponding spec directory under specs/ for the detected prefix to ensure alignment with the spec workflow.
  • Works in environments where Git is available and provides graceful fallback when Git is not present or not a repository.

Quick Start

Run the speckit-git-validate tool in your repository to confirm the current branch matches the accepted patterns and to verify the existence of a matching 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 enforce feature branch naming conventions in Git?▼

To enforce feature branch naming conventions, validate current Git branches against sequential patterns like 001-feature-name or timestamped patterns like 20260319-143022-feature-name. This confirms branches match predefined specs and avoids misnamed branch workflow issues.

What Git branch naming patterns are valid for spec workflows?▼

Valid Git branch naming patterns for spec workflows include sequential names like 001-feature-name and timestamped names like 20260319-143022-feature-name. Matching prefixes must have corresponding spec directories under specs/ to ensure alignment.

Do I need Git installed to validate branch names against specs directories?▼

You do not need Git installed to validate branch names. If Git is unavailable or not a repository, validation falls back to the SPECIFY_FEATURE environment variable when provided, otherwise skipping with a warning.

How do I check if a Git branch has a matching specs directory?▼

To check if a Git branch has a matching specs directory, validate the branch name against allowed patterns and verify a corresponding spec directory exists under specs/ with a matching prefix like 001 or a timestamp.

What happens when Git branch validation fails in non-repository environments?▼

When Git branch validation fails in non-repository environments, the tool skips validation with a warning unless the SPECIFY_FEATURE environment variable is provided, in which case it uses that value for fallback validation.

Related Skills

Explore More Software Engineering Skills→
alienstroalienstro

speckit-git-validate

Validate Git branch names against speckit conventions and spec directory existence.

Community
Intermediate
EzekTec-IncEzekTec-Inc

speckit-git-validate

Validate Git feature branch naming and matching specification directories.

Community
Intermediate
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
FelipePepeFelipePepe

rule-gitflow

Enforce standardized Git workflows with Conventional Commits and Husky hooks.

Community
Intermediate