speckit-git-validate

Validate Git feature branch names against sequential or timestamp patterns.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-git-validate-omerkllm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/omerkllm/edris-antigravity/tree/main/.agent/skills/speckit-git-validate
Command: npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-git-validate-omerkllm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that the current Git branch follows the expected feature branch naming conventions and provide guidance on branch validation.

Core Features & Use Cases

  • Branch pattern validation: recognizes Sequential (e.g., 001-feature) and Timestamp (e.g., 20260319-143022-feature) patterns and verifies both the branch name and presence of corresponding specs directories when applicable.
  • Status reporting: prints on-feature results, including whether a matching spec directory exists under specs/, or warns if missing.
  • Graceful degradation: falls back to SPECIFY_FEATURE when Git is unavailable or not in a repository, with clear guidance.

Quick Start

Run the validation on your current repository to verify your feature branch naming and related specs.

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 conventions, the Skill checks the current branch name against sequential (e.g., 001-feature) and timestamp (e.g., 20260319-143022-feature) patterns, reporting matches and whether corresponding specs directories exist.

What patterns are supported for feature branch naming validation?▼

Feature branch naming validation supports Sequential patterns like 001-feature and Timestamp patterns like 20260319-143022-feature, verifying the branch name structure and checking if a matching spec directory exists under specs/.

Can I check branch naming rules without a Git repository?▼

Yes, you can check branch naming rules without a Git repository. The Skill gracefully degrades by reading the SPECIFY_FEATURE environment variable and validating its value against the defined naming rules.

How do I verify if a specs directory exists for my current branch?▼

To verify if a specs directory exists for your current branch, the Skill checks whether a corresponding directory is present under specs/ after confirming the branch name matches sequential or timestamp patterns, warning you if it is missing.

What happens if my Git branch name does not match the expected pattern?▼

If your Git branch name does not match the expected pattern, the Skill reports the non-compliance and provides guidance on branch validation rather than executing further spec directory checks.