speckit-git-validate

Validate current Git branch names against feature-branch naming patterns.

Updated May 16, 2026
One-click install
npx skills add https://github.com/WeihanLi/Spark.OpenXml --skill speckit-git-validate-weihanli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/WeihanLi/Spark.OpenXml/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/WeihanLi/Spark.OpenXml --skill speckit-git-validate-weihanli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure that feature branches adhere to a consistent naming scheme, improving traceability and review workflow.

Core Features & Use Cases

  • Validates current branch name against two patterns: a sequential 3+ digit prefix and a timestamp-based prefix.
  • Reports whether you are on a valid feature branch and whether a corresponding spec directory exists under specs/.
  • Gracefully degrades by using the SPECIFY_FEATURE environment variable as a fallback when Git is unavailable or not a repository.

Quick Start

Validate the current branch name against the defined feature-branch patterns to verify compliance.

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 feature-branch naming conventions?

To validate Git branch naming, the Skill checks the current branch against sequential 3+ digit prefixes and timestamp-based patterns. It outputs feature-branch compliance status and verifies if a matching spec directory exists under specs/.

What is a feature-branch naming convention in Git workflows?

A feature-branch naming convention standardizes branch names for better traceability. This Skill enforces it by matching branch names against sequential 3+ digit prefixes or timestamp-based prefixes to ensure consistent review workflows.

Does the branch validation tool work without a local Git repository?

Yes, branch validation works without a local Git repository. When Git is unavailable, the Skill gracefully degrades and uses the SPECIFY_FEATURE environment variable as a fallback to determine the feature-branch status.

How do I check if a spec directory exists for my current feature branch?

To check if a spec directory exists, the Skill validates the current Git branch name and searches for a corresponding directory under specs/. It reports whether the matching spec directory is present for the active feature branch.

What Git branch name patterns are supported for feature-branch validation?

Supported Git branch name patterns include a sequential 3+ digit prefix and a timestamp-based prefix. The Skill validates the current branch against these two specific patterns to enforce feature-branch naming rules.