skills.rest
BOUROUIS-MOHAMED
BOUROUIS-MOHAMEDCOMMUNITY
Explore all skills by this author →
GitHub

speckit-git-validate

Validate current Git branch names against Speckit feature-naming conventions.

Updated Dec 26, 2025
Search Tags:#git#workflow#validation#branch#speckit#naming#specs
One-click install
npx skills add https://github.com/BOUROUIS-MOHAMED/monclub_access_python --skill speckit-git-validate-bourouis-mohamed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/BOUROUIS-MOHAMED/monclub_access_python/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/BOUROUIS-MOHAMED/monclub_access_python --skill speckit-git-validate-bourouis-mohamed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams enforce consistent Git branch naming to improve traceability and enable automated Speckit validation workflows.

Core Features & Use Cases

  • Branch naming validation for feature branches with support for sequential prefixes (e.g., 001-feature) and timestamp prefixes (e.g., 20260319-143022-feature).
  • Checks for a corresponding spec directory under specs/ to ensure associated work artifacts exist.
  • Graceful fallback when Git is unavailable, with optional SPECIFY_FEATURE environment variable support.

Quick Start

Invoke the speckit-git-validate skill on a repository to verify the current branch name aligns with the 3-digit sequential or timestamp prefix rules.

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 branch naming conventions for Speckit feature branches?▼

Speckit feature-branch naming validation checks the current Git branch against sequential prefixes like 001-feature-name and timestamp prefixes like 20260319-143022-feature, then reports whether a corresponding spec directory exists under specs/.

What is the correct feature-branch naming format for Speckit workflows?▼

The correct format for Speckit workflows uses either a 3-digit sequential prefix such as 001-feature-name or a timestamp prefix such as 20260319-143022-feature to maintain consistent branch traceability.

Can I check Speckit branch naming without Git installed in my environment?▼

You can validate branch naming without Git by setting the SPECIFY_FEATURE environment variable as a fallback, allowing the skill to gracefully handle environments without Git installed.

Does Speckit branch validation check for corresponding spec directories?▼

Yes, Speckit branch validation checks for a corresponding spec directory under specs/ to ensure associated work artifacts exist alongside the named feature branch.

Why does my Git branch name fail Speckit validation despite following a prefix pattern?▼

Your Git branch fails Speckit validation if it does not strictly match the 001-feature sequential prefix or 20260319-143022-feature timestamp prefix, or if no matching spec directory exists under specs/.

Related Skills

Explore More Software Engineering Skills→
alienstroalienstro

speckit-git-validate

Validate Git branch names against speckit conventions and spec directory existence.

Community
Intermediate
kerolos-saaidkerolos-saaid

speckit-plan

Automate implementation planning to generate design artifacts from feature specifications.

Community
Advanced
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced
brianpunzalanbrianpunzalan

speckit-git-validate

Validates Git branch names and ensures corresponding spec directories exist.

Community
Intermediate