skills.rest
engakhattab
engakhattabCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-git-validate

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

Updated Aug 23, 2025
Search Tags:#git#spec-kit#branch naming#repository validation#CI guardrail#folder existence
One-click install
npx skills add https://github.com/engakhattab/DEPI_Angular_project --skill speckit-git-validate-engakhattab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/engakhattab/DEPI_Angular_project/tree/main/Backend/HR/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/engakhattab/DEPI_Angular_project --skill speckit-git-validate-engakhattab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or inconsistent feature work by checking whether your current Git branch name follows the expected feature naming patterns and whether a matching spec directory exists.

Core Features & Use Cases

  • Branch naming validation: Confirms the current branch matches sequential or timestamp-based feature naming formats (for example, 001-feature-name or 20260319-143022-feature-name).
  • Spec directory alignment check: Verifies the corresponding spec folder exists under specs/ for the branch prefix, helping ensure the feature has its required specification.
  • Graceful degradation: If Git is unavailable or you are not in a Git repo, it falls back to validating a SPECIFY_FEATURE environment variable when provided.

Quick Start

Run the skill in your repo to validate the current branch name and confirm whether its spec 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 a Git branch name against feature naming conventions?▼

Spec directory alignment verifies that a matching spec folder exists under specs/ for the branch prefix. This ensures the feature has its required specification before development proceeds.

What happens if Git is unavailable when running repository validation?▼

If Git is unavailable or you are not in a Git repo, repository validation falls back to checking the SPECIFY_FEATURE environment variable. This allows graceful degradation when Git access is blocked.

Can I use this validation in a CI pipeline as a guardrail for spec-kit repositories?▼

Yes, you can use this validation in a CI pipeline as a guardrail for spec-kit repositories. It enforces pattern matching and folder existence checks, outputting success or clear warnings to prevent inconsistent feature work.

Does branch naming validation support timestamped feature formats?▼

Branch naming validation supports timestamped feature formats like 20260319-143022-feature-name alongside sequential schemes. It applies pattern matching to confirm the current Git branch follows expected spec-kit naming conventions.

Related Skills

Explore More Software Engineering Skills→
eavichayeavichay

git-validate

Validate Git branch names against sequential, timestamp, or custom patterns.

Community
Intermediate
tykhoncodetykhoncode

speckit-git-validate

Validate Git feature branch names and matching spec directories.

Community
Intermediate
TKlerxTKlerx

speckit-git-commit

Automatically stage and commit changes after Spec Kit command execution.

Community
Basic
PieroSierraPieroSierra
128

speckit-git-validate

Validate Git feature branch names against predefined naming patterns.

Community
Basic