skills.rest
inspedralbes
inspedralbesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-git-validate

Validate Git branch names against sequential or timestamp feature-branch patterns.

Updated Apr 10, 2026
Search Tags:#automation#git#workflow#devops#validation#branching#specs
One-click install
npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill speckit-git-validate-inspedralbes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW/tree/main/prj-entrades-nou/.cursor/skills/speckit-git-validate
Command: npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill speckit-git-validate-inspedralbes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that the current Git branch adheres to the project’s feature-branch naming conventions and ensures corresponding spec directories exist when applicable.

Core Features & Use Cases

  • Branch name validation against two patterns: sequential (e.g., 001-feature) and timestamp (e.g., 20260319-143022-feature).
  • Spec directory presence check under specs/ for valid branches, surfacing warnings when missing.
  • Graceful degradation when Git is unavailable or the repository isn’t a Git repo, with optional SPECIFY_FEATURE fallback.

Quick Start

Run speckit-git-validate in your repository to verify the active branch name and the corresponding 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 validate Git branch naming conventions automatically?▼

It validates Git branch naming conventions by checking the active branch against sequential (000-feature) or timestamp (YYYYMMDD-HHMMSS-feature) patterns, reporting clear status messages if the branch name fails to match the expected structure.

How do I check if a matching specs directory exists for my feature branch?▼

It checks for matching specs directories by scanning the specs/ path after validating the branch name, surfacing clear warnings when the expected spec directory corresponding to the active feature branch is missing from the repository.

Does branch validation work without Git installed on my machine?▼

Branch validation degrades gracefully when Git is unavailable or the directory is not a Git repository, handling the missing dependency smoothly and optionally applying a SPECIFY_FEATURE fallback to continue processing without crashing.

What Git branch naming patterns are supported for feature-branch validation?▼

Feature-branch validation supports two naming patterns: sequential formats like 000-feature and timestamp formats like YYYYMMDD-HHMMSS-feature, ensuring branch names align with the project's established conventions before checking specs directories.

When should I run Git branch validation in my development workflow?▼

Run Git branch validation during local development workflows before committing changes or opening pull requests, ensuring the active branch adheres to naming conventions and corresponding specs directories exist to prevent downstream integration issues.

Related Skills

Explore More Software Engineering Skills→
kentojekentoje
2

jira

View and manage Jira tickets from the command line.

Community
Advanced
reedomreedom

detect-kiro-specs

Detect modified Kiro specs in the current branch using git diff.

Community
Basic
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate
tykhoncodetykhoncode

speckit-git-validate

Validate Git feature branch names and matching spec directories.

Community
Intermediate