skills.rest
EzekTec-Inc
EzekTec-IncCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-git-validate

Validate Git feature branch naming and matching specification directories.

Updated May 11, 2026
Search Tags:#git#workflow#repository#spec-kit#feature branches#branch validation
One-click install
npx skills add https://github.com/EzekTec-Inc/cade --skill speckit-git-validate-ezektec-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/EzekTec-Inc/cade/tree/main/mcp-ui-tui-plugin/.claude/skills/speckit-git-validate
Command: npx skills add https://github.com/EzekTec-Inc/cade --skill speckit-git-validate-ezektec-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers catch invalid Git branch naming and missing specification directory issues before they disrupt spec-driven development workflows.

Core Features & Use Cases

  • Branch Pattern Validation: Checks whether the current Git branch follows supported sequential or timestamp-based feature naming conventions.
  • Spec Directory Verification: Confirms that matching feature specification directories exist under the specs folder.
  • Graceful Fallback Handling: Supports validation through repository checks or the SPECIFY_FEATURE environment variable when Git context is unavailable.

Quick Start

Use the speckit-git-validate skill to verify that the current branch follows spec-kit feature branch conventions and has a matching specification 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 feature branch naming conventions?▼

To validate Git feature branch naming, the skill checks the current repository branch against supported sequential or timestamp-based feature naming patterns to ensure spec-kit workflow compliance.

How do I verify that a matching specification directory exists for my feature branch?▼

Spec directory verification confirms that a matching feature specification directory exists under the specs folder for the active branch, preventing missing spec issues in spec-driven development.

Can I validate feature branches without direct Git repository access?▼

Yes, you can validate feature branches without Git access by using the SPECIFY_FEATURE environment variable as a fallback to verify supported branch patterns and related specs.

What are the supported Git branch naming patterns for spec-kit workflows?▼

Supported Git branch naming patterns for spec-kit workflows include sequential and timestamp-based feature naming conventions, which are checked during branch validation to maintain compliance.

When should I use branch validation in a spec-driven development workflow?▼

Use branch validation in spec-driven workflows before integrating changes to catch invalid Git branch naming and missing specification directories early, preventing disruption to feature tracking.

Related Skills

Explore More Software Engineering Skills→
juvenaljuvenal
8

speckit-git-validate

Validate Git feature branch names against sequential or timestamp patterns.

Community
Intermediate
infantesromeroadrianinfantesromeroadrian

speckit-specify

Generate a feature specification document from a natural language description.

Community
Advanced
PiklarPiklar

speckit-taskstoissues

Convert project tasks into dependency-ordered GitHub issues.

Community
Advanced
PiklarPiklar

speckit-git-validate

Validate Git branch names against sequential or timestamp patterns and check spec directories.

Community
Intermediate