skills.rest
NUMU-IO
NUMU-IOOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-git-validate

Validates the current Git branch against feature naming conventions.

2|Updated Jan 6, 2026
Search Tags:#git#feature branches#branch validation#spec directory#workflow compliance#repository checks
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-git-validate-numu-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-git-validate-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly confirm whether the current Git branch follows the expected feature branch naming rules, reducing confusion and preventing workflow mistakes during spec-driven development.

Core Features & Use Cases

  • Branch Validation: Checks whether the active branch uses a sequential or timestamp-based feature naming pattern.
  • Spec Directory Check: Looks for a matching spec directory so branch work can be tied to the right feature context.
  • Graceful Fallbacks: Handles environments without Git by using a fallback value when available.
  • Use Case: A developer opens a new task branch and uses this Skill to verify that the branch name and related spec folder are aligned before continuing work.

Quick Start

Ask the Skill to validate the current branch name and report whether a matching spec directory exists.

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 name against my spec directory?▼

Git branch validation checks the active branch against sequential or timestamp-based naming conventions and verifies a matching spec directory exists to ensure spec-driven workflow compliance.

What is a spec-driven development workflow for feature branch naming?▼

A spec-driven workflow uses sequential or timestamp-prefixed feature branch names tied to matching spec directories, ensuring branch work remains aligned with the correct feature context and documentation.

How do I check if my current Git branch matches sequential or timestamp naming rules?▼

You can check branch pattern compliance by validating the current Git branch name against expected sequential or timestamp-based feature naming conventions to prevent workflow mistakes before continuing work.

Does branch validation work when Git is unavailable in the environment?▼

Branch validation handles environments without Git by using a fallback value when available, ensuring graceful degradation so repository checks can still proceed in limited contexts.

Why do I need to verify my feature branch before starting spec-driven development?▼

Verifying your feature branch confirms the branch name and related spec folder are aligned, reducing confusion and preventing workflow mistakes that occur when branch context and spec directories mismatch.

What's the best way to automate repository checks for feature branch compliance?▼

Automating repository checks involves validating the current Git branch against feature naming conventions and confirming the spec directory presence, providing immediate feedback on branch pattern compliance.

Related Skills

Explore More Software Engineering Skills→
alienstroalienstro

speckit-git-validate

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

Community
Intermediate
warpdotdevwarpdotdev
292

implement-specs

Plan and execute feature implementations while keeping specs aligned with code changes.

Official
Advanced
cbleckercblecker
5

creating-branch

Create a feature branch from the current Git state with conventional naming.

Community
Basic
alfredoperezalfredoperez
80

speckit-git-validate

Validate Git branch names against Spec-Kit naming conventions.

Community
Basic