speckit.git.validate

Validate current Git branch names against feature-branch patterns and spec directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that the current Git branch adheres to predefined feature-branch naming conventions, reducing confusion and drift in development workflows.

Core Features & Use Cases

  • Validates the active branch name against two patterns: a sequential numeric prefix (e.g., 001-feature) and a timestamp-based prefix (e.g., 20260319-143022-feature).
  • Checks for a corresponding spec directory under specs/ to ensure a linked validation workflow exists.
  • Gracefully degrades when Git is unavailable or not inside a repository, optionally using the SPECIFY_FEATURE env var as a fallback.

Quick Start

Run this skill to verify that your current Git branch name conforms to the feature-branch 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 a Git feature-branch naming convention in my workflow?

To validate a Git feature-branch naming convention, this Skill checks the active branch against predefined sequential numeric and timestamp-based prefixes, reporting compliance outcomes. It verifies patterns like 001-feature or 20260319-143022-feature.

What is the required format for Git branch names to pass spec validation?

The required format for Git branch names to pass spec validation uses either a sequential numeric prefix like 001-feature or a timestamp-based prefix like 20260319-143022-feature. The Skill enforces these patterns to prevent development drift.

Can I validate branch naming if Git is not installed or I am not in a repository?

You cannot fully validate branch naming if Git is not installed, but this Skill gracefully degrades in such environments. When outside a Git repository, it optionally uses the SPECIFY_FEATURE environment variable as a fallback.

How do I link my Git branch to a matching spec directory under specs?

To link your Git branch to a spec directory under specs, this Skill checks for a corresponding spec directory matching the branch name during validation. This ensures a linked validation workflow exists for your feature.

What happens if my current Git branch name does not match the expected feature patterns?

If your current Git branch name does not match the expected feature patterns, the Skill reports the non-compliance outcome. It detects Git availability and verifies the branch against sequential and timestamp prefixes to enforce standards.