speckit-git-validate

Validate Git branch names against sequential or timestamp feature patterns.

Updated May 18, 2026
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-git-validate-kamijeong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-git-validate-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps verify whether the current Git branch follows the expected feature-branch naming rules, reducing workflow mistakes before validation or review.

Core Features & Use Cases

  • Branch Name Validation: Confirms that the active branch uses either a sequential numeric prefix or a timestamp-based prefix.
  • Spec Directory Check: Looks for the matching specs/ directory for the branch prefix and reports whether the related spec exists.
  • Graceful Fallbacks: Warns and skips validation when Git is unavailable, or falls back to the SPECIFY_FEATURE environment variable when needed.

Quick Start

Ask the skill to validate the current branch and report whether it matches the expected feature-branch naming convention.

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 names against feature branch conventions?▼

Git branch name validation checks the active branch against sequential numeric or timestamp-based prefixes to ensure compliance with feature-branch naming rules before review. It confirms the prefix matches the expected format and looks for the corresponding spec directory.

What is a Spec Kit repository and when do I need branch-to-spec traceability?▼

Spec Kit repository branch-to-spec traceability links a feature branch prefix to a matching specs/ directory. You need it when your workflow requires verifying that a branch name corresponds to an existing spec before allowing validation or shipping.

How do I check if a specs directory exists for my current git branch prefix?▼

To check if a specs directory exists for your git branch prefix, validate the branch name to extract its sequential or timestamp prefix, then search for a matching specs/ directory within the repository to confirm spec existence.

Can I validate branch naming rules when git is unavailable in my environment?▼

You can validate branch naming rules when git is unavailable by using a graceful fallback that checks the SPECIFY_FEATURE environment variable. If git is missing and the variable is unset, the validation warns and skips.

What are the limitations of automated branch validation gating in Spec Kit repositories?▼

Limitations of branch validation gating include skipping the process entirely when git is not installed and relying on the SPECIFY_FEATURE environment variable as a fallback, which may not reflect the actual active branch state.