skills.rest
domattioli
domattioliCOMMUNITY
Explore all skills by this author →
GitHub

speckit-git-validate

Validate Git branch names against sequential or timestamp feature patterns.

Updated Aug 23, 2026
Search Tags:#git#workflow#validation#branching#naming-conventions#specs
One-click install
npx skills add https://github.com/domattioli/DomI --skill speckit-git-validate-domattioli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/domattioli/DomI/tree/main/.claude/skills/speckit-git-validate
Command: npx skills add https://github.com/domattioli/DomI --skill speckit-git-validate-domattioli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Git feature branches follow established naming conventions to improve traceability, review, and automation readiness in spec-driven workflows.

Core Features & Use Cases

  • Validates that the current branch matches one of the recognized feature naming patterns (sequential like 001-feature-name or timestamp like 20260319-143022-feature-name).
  • Verifies the existence of a corresponding spec directory under specs/ for the detected branch prefix.
  • Provides graceful degradation by using a SPECIFY_FEATURE fallback when Git is unavailable or the repository is not a project using Git.

Quick Start

Run the speckit-git-validate skill to verify that your current Git branch follows the feature naming conventions.

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?▼

Validate Git feature branch naming by checking the current branch against sequential patterns like 001-feature-name or timestamp patterns like 20260319-143022-feature-name to ensure traceability and automation readiness in spec-driven workflows.

What are the recognized Git feature branch naming patterns for spec-driven workflows?▼

Recognized Git feature branch naming patterns include sequential formats such as 001-feature-name and timestamp formats such as 20260319-143022-feature-name, which improve traceability and review in spec-driven software projects.

Does Git branch validation check for corresponding spec directories?▼

Git branch validation checks for a corresponding spec directory by reporting whether a matching specs/ mapping exists under the specs/ folder for the identified branch prefix.

Can I validate branch naming without a Git repository?▼

You can validate branch naming without a Git repository by using the SPECIFY_FEATURE environment variable as a fallback, which allows graceful degradation when Git is unavailable or the directory is not a Git repo.

Why should my software project enforce Git feature branch naming conventions?▼

Enforcing Git feature branch naming conventions improves traceability, review, and automation readiness by ensuring branches follow established sequential or timestamp patterns mapped to spec directories.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
jimmymalhanjimmymalhan
1

auto-merge

Merge pull requests automatically after CI checks pass.

Community
Intermediate
PieroSierraPieroSierra
128

speckit-git-validate

Validate Git feature branch names against predefined naming patterns.

Community
Basic
Rubiss-ProjectsRubiss-Projects
25

speckit-git-validate

Validate Git branch names against sequential or timestamped naming patterns.

Official
Basic