skills.rest
sethdavis512
sethdavis512COMMUNITY
Explore all skills by this author →
Website𝕏@sethdavis512GitHub

speckit-git-validate

Validates that the current Git branch follows spec-kit feature branch naming conventions.

4|Updated Oct 24, 2025
Search Tags:#git#feature branch#spec-driven development#spec-kit#naming convention#branch validation
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-git-validate-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/sethdavis512/iridium/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-git-validate-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using spec-kit workflows need feature branches to follow strict naming conventions so that specs, branches, and directories stay linked. Manually checking branch names against patterns like 001-feature-name or 20260319-143022-feature-name is error-prone and easy to skip. ## Core Features & Use Cases - Branch name validation: Checks the current Git branch against sequential (NNN-name) and timestamp (YYYYMMDD-HHMMSS-name) naming patterns. - Spec directory detection: Verifies that a matching directory exists under specs/ for the branch prefix and reports whether it was found. - Graceful degradation: Falls back to the SPECIFY_FEATURE environment variable or skips with a warning when Git is unavailable. - Use Case: Before running a spec-kit planning command, validate that you are on branch 042-fix-bug and confirm the specs/042-* directory exists so downstream commands resolve the correct feature context. ## Quick Start Validate that my current Git branch follows the spec-kit feature branch naming convention and check for its matching 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 a Git feature branch name in a spec-kit project?▼

Run the validation to compare the current branch from git rev-parse --abbrev-ref HEAD against two patterns: sequential names like 001-feature-name and timestamp names like 20260319-143022-feature-name. It reports whether the branch matches and whether a corresponding spec directory exists.

What branch naming conventions does spec-kit use?▼

Spec-kit feature branches use either a sequential numeric prefix of three or more digits followed by a hyphen, such as 042-fix-bug, or a timestamp prefix in YYYYMMDD-HHMMSS format, such as 20260319-143022-feature-name.

What happens if Git is not installed or the directory is not a repository?▼

The validation degrades gracefully by checking the SPECIFY_FEATURE environment variable as a fallback and validating that value against the same naming patterns. If neither is available, it outputs a warning and skips validation.

Why does branch validation report no spec directory found?▼

The branch prefix has no matching directory under specs/. For sequential branches it looks for specs/<prefix>-* using the numeric portion, and for timestamp branches it uses the YYYYMMDD-HHMMSS portion. Create the spec directory or rename the branch to match an existing one.

Related Skills

Explore More Software Engineering Skills→
ApothecaryManApothecaryMan

speckit-git-feature

Generate and switch to numbered Git feature branches in spec-kit projects.

Community
Basic
WU-MAO-CHIAWU-MAO-CHIA

speckit-git-validate

Validates Git branch names against spec-kit feature branch naming conventions.

Community
Basic
unipds-engenharia-de-ia-aplicadaunipds-engenharia-de-ia-aplicada
1.0k

speckit-git-validate

Validate Git branch names against feature branch naming conventions.

Official
Intermediate
astrum-forgeastrum-forge

physics

Adds Havok-based 3D rigid body physics, colliders, and queries to ignifx games.

Official
Advanced