skills.rest
alienstro
alienstroCOMMUNITY
Explore all skills by this author →
GitHub

speckit-git-validate

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

Updated Apr 23, 2026
Search Tags:#git#naming conventions#spec-kit#branch validation#feature workflow#filesystem checks
One-click install
npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-git-validate-alienstro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/alienstro/mediapipe-scroll/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-git-validate-alienstro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents mismatches between your current Git feature branch name and the expected spec directory structure, so teams fail fast before running spec-kit dependent steps.

Core Features & Use Cases

  • Feature-branch naming validation: Checks whether the current branch matches sequential or timestamp-based naming patterns.
  • Spec directory existence check: Verifies that the corresponding specs/<prefix>-* directory exists for the detected branch prefix.
  • Graceful fallback behavior: If Git is unavailable, it can validate a branch-like value from the SPECIFY_FEATURE environment variable; otherwise it skips with a clear warning.

Quick Start

Validate your branch and confirm the matching specs/<prefix>-* directory exists by running this skill inside a spec-kit project checkout.

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 my Git branch name against spec-kit feature conventions?▼

To validate a Git branch name against spec-kit conventions, run the skill inside your repository to parse the current branch and verify it matches sequential or timestamp-based feature naming patterns.

How does spec-kit branch validation check for matching spec directories?▼

Spec-kit branch validation checks for matching spec directories by parsing the branch prefix and confirming that a corresponding `specs/<prefix>-*` folder exists in your project filesystem.

Do I need a Git repository to run spec-kit branch validation?▼

You do not need a Git repository to run spec-kit branch validation, as it gracefully falls back to checking a branch-like value from the `SPECIFY_FEATURE` environment variable when Git is unavailable.

Why does spec-kit workflow fail when my feature branch name mismatches the spec directory?▼

Spec-kit workflows fail when branch names mismatch the spec directory because dependent steps require `specs/`-prefixed folders to align with sequential and timestamp feature branches to process correctly.

What are the limitations of using environment variables for spec-kit feature branch validation?▼

The limitation of using environment variables for spec-kit branch validation is that if Git is unavailable and `SPECIFY_FEATURE` is not set, the skill skips validation entirely and only outputs a warning.

Related Skills

Explore More Software Engineering Skills→
KamiJeongKamiJeong

speckit-git-feature

Create a numbered git feature branch for Spec Kit projects.

Community
Intermediate
B0yZ4kr14B0yZ4kr14

speckit-git-validate

Validate Git feature branch naming and spec directory mapping.

Community
Intermediate
omerkllmomerkllm

speckit-git-validate

Validate Git feature branch names against sequential or timestamp patterns.

Community
Intermediate
juvenaljuvenal
8

speckit-git-validate

Validate Git feature branch names against sequential or timestamp patterns.

Community
Intermediate