speckit-git-validate

Validate current Git branch names against feature naming conventions and spec directories.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/arosenkranz/kranz-tv --skill speckit-git-validate-arosenkranz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/arosenkranz/kranz-tv/tree/main/.claude/skills/speckit-git-validate
Command: npx skills add https://github.com/arosenkranz/kranz-tv --skill speckit-git-validate-arosenkranz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Git branches follow consistent feature-focused naming to improve traceability and alignment with specs.

Core Features & Use Cases

  • Validates two naming patterns: sequential prefixes (e.g., 001-feature) and timestamped prefixes (e.g., 20260319-143022-feature), ensuring branch names reflect intent and timing.
  • Verifies that a corresponding spec directory exists under specs/ for the identified feature prefix, enabling end-to-end validation when specs are present.
  • Provides graceful degradation when Git is unavailable or not a repository, suggesting fallbacks or environment variables as needed.

Quick Start

Run this skill in a Git-enabled project to verify that the current branch conforms to the defined feature naming 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 enforce Git feature branch naming conventions automatically?▼

Feature branch naming validation checks the current Git branch against predefined patterns like sequential prefixes (001-feature) or timestamped prefixes (20260319-143022-feature) to ensure traceability and alignment with project specs.

What are the standard Git branch naming patterns for feature workflows?▼

Standard Git branch naming patterns for features include sequential prefixes (e.g., 001-feature) and timestamped prefixes (e.g., 20260319-143022-feature). These patterns ensure branch names reflect development intent and timing for better traceability.

How do I verify a spec directory exists for my current Git feature branch?▼

Spec directory validation checks for a corresponding specs/ directory matching the identified feature prefix extracted from the Git branch name. This enables end-to-end validation when specs are present in the repository.

Does branch naming validation work without Git installed or outside a repository?▼

Branch naming validation works without Git by handling cases where Git is unavailable or the directory is not a repository. It emits informative messages and suggests optional fallbacks or environment variables as needed.

What is the best way to link Git branch names to spec directories?▼

The best way to link Git branch names to spec directories is to validate the branch name's feature prefix and verify a matching specs/ directory exists. This ensures alignment between the branch intent and the defined specifications.