speckit-git-validate

Validate current Git branch names against sequential and timestamp naming conventions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce consistent feature branch naming to improve traceability and automation in Git workflows.

Core Features & Use Cases

  • Validates that the current Git branch follows predefined feature naming conventions (sequential and timestamp formats).
  • Detects whether a corresponding spec directory exists under specs/ for the current branch prefix.
  • Gracefully degrades when Git is not available by using the SPECIFY_FEATURE environment variable as a fallback.

Quick Start

Run the validation on your repository to verify the current branch name and locate the matching specs 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 Git branch naming conventions automatically?

To validate Git branch naming conventions automatically, run this validation on your local repository to check if the current branch follows predefined sequential and timestamp formats. It reads the branch name using git rev-parse and reports traceability compliance.

What is feature branch naming validation in a spec-kit structure?

Feature branch naming validation in a spec-kit structure is the process of verifying that your current Git branch matches expected naming patterns and optionally mapping it to a corresponding specs/ directory to ensure documentation traceability.

Do I need Git installed to check feature branch naming patterns?

You do not strictly need Git installed to check feature branch naming patterns; the validation gracefully degrades by using the SPECIFY_FEATURE environment variable as a fallback when Git is not available.

Can I detect if a specs directory exists for my current Git branch prefix?

You can detect if a specs directory exists for your current Git branch prefix; the validation checks your local spec-kit structure and reports whether a corresponding spec directory exists under the specs/ path.

What Git branch naming formats are supported for traceability validation?

The traceability validation supports predefined sequential and timestamp naming formats to ensure your feature branches align with automation workflows and maintain consistent repository history.