speckit-git-validate

Validate Git branch names against prefix patterns and check spec directories.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill speckit-git-validate-majedsiefalnasr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/majedsiefalnasr/bunyan-app-cursor/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill speckit-git-validate-majedsiefalnasr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that the current Git branch follows the required feature-branch naming conventions and verify the existence of a corresponding spec directory when present.

Core Features & Use Cases

  • Enforces patterns for sequential prefixes like 001-feature-name and timestamp prefixes like 20260319-143022-feature-name.
  • Checks for a matching specs/<prefix>-* directory when a valid feature branch is detected.
  • Provides graceful degradation when Git is unavailable or the repository is not in a Git workspace.

Quick Start

Run speckit-git-validate in your project root to verify the current branch name against allowed patterns and locate its spec 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 enforce Git feature-branch naming conventions in my repository?

To enforce Git feature-branch naming conventions, you can validate current branch names against specific patterns like 001-feature-name or timestamp prefixes such as 20260319-143022-feature-name. This ensures branches follow your required sequential or timestamp formats.

Can I check if a Git branch has a corresponding specs directory?

Yes, you can check for a matching specs directory by validating the current Git branch name and locating a corresponding specs/<prefix>-* directory. This verifies that a valid feature branch has the expected spec folder structure present.

What Git branch naming patterns are supported for feature branches?

Supported Git branch naming patterns include sequential prefixes like 001-feature-name and timestamp prefixes like 20260319-143022-feature-name. These patterns enforce consistent formatting for feature branches in your repository.

What happens if Git is unavailable or I'm not in a Git workspace?

If Git is unavailable or the repository is not in a Git workspace, the validation process provides graceful degradation. This means it handles missing Git environments without failing, ensuring the process exits smoothly.

How do I validate a timestamp-prefixed Git branch name?

To validate a timestamp-prefixed Git branch name, check it against the pattern ^[0-9]{8}-[0-9]{6}-. This recognizes timestamp formats like 20260319-143022-feature-name and verifies the corresponding spec directory exists.