speckit-git-validate

Validate Git branch names against feature naming conventions and spec directory existence.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Congtrinhh/sholy-be --skill speckit-git-validate-congtrinhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/Congtrinhh/sholy-be/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/Congtrinhh/sholy-be --skill speckit-git-validate-congtrinhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps prevent misnamed feature branches by automatically checking whether the current Git branch follows the repository’s expected naming patterns, reducing downstream workflow friction.

Core Features & Use Cases

  • Feature-branch naming validation: Confirms the current branch matches either a sequential numeric prefix or a timestamp prefix pattern.
  • Spec directory presence check: Verifies that a corresponding spec folder exists under specs/ for the branch prefix, helping catch missing specs early.
  • Graceful fallback when Git is unavailable: Uses the SPECIFY_FEATURE environment variable to validate naming even outside a Git workspace.

Quick Start

Run the speckit-git-validate validation on your current branch to confirm it matches the expected feature naming pattern and that a matching specs directory exists.

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 automatically?

You can validate branch naming by checking the current Git branch against sequential numeric or timestamp prefix patterns. This ensures feature branches match repository expectations and reduces downstream workflow friction.

How do I check if a specs directory exists for my feature branch prefix?

Spec directory presence is verified by checking for a corresponding folder under specs/ matching the branch prefix. This filesystem check catches missing specs early during spec-kit project maintenance and feature branch preparation.

Can I validate feature branch names outside a Git workspace?

Feature branch names can be validated outside a Git workspace using the SPECIFY_FEATURE environment variable. This fallback mechanism enforces naming pattern checks when Git is unavailable, ensuring CI readiness without a local repository.

Why does my feature branch fail CI readiness checks?

CI readiness checks fail when branch names do not match expected sequential or timestamp prefix patterns, or when the corresponding spec directory under specs/ is missing. Workflow guardrails catch these mismatches early.

What is the best way to enforce workflow guardrails for spec-kit branch creation?

Enforcing workflow guardrails during spec-kit branch creation involves validating branch naming conventions and verifying corresponding spec folders. Applying these filesystem and Git checks prevents misnamed branches and missing specs early.

Does speckit-git-validate work without any external dependencies?

speckit-git-validate operates without external dependencies, using standard Git commands and filesystem checks. It relies only on Git for branch detection and the SPECIFY_FEATURE variable as a fallback environment input.