speckit-git-validate

Validate Git feature branch names against naming patterns and spec directories.

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-git-validate-apothecaryman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-git-validate-apothecaryman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the current Git branch follows the expected feature branch naming conventions, reducing the risk of merge conflicts and streamlining the code review process.

Core Features & Use Cases

  • Branch Naming Validation: Validates that the current branch name matches specific patterns for sequential or timestamped naming conventions.
  • Spec Directory Check: Checks for the existence of a corresponding spec directory under specs/ based on the branch naming.
  • Output Messages: Provides clear feedback on whether the branch is valid, if a spec directory is found, or if the branch is not a feature branch.

Quick Start

Run the 'speckit-git-validate' skill to validate the current branch naming conventions.

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 feature branch naming conventions automatically?

To validate Git feature branch naming conventions automatically, you can run validation checks using regular expressions to match specific sequential or timestamped naming patterns. This ensures branches follow expected formats and reduces merge conflicts.

How do I check if a spec directory exists for my current Git branch?

Checking for a spec directory involves validating the current Git branch name and looking for a corresponding directory under the specs/ path. This confirms the branch has the expected spec-kit project structure set up correctly.

Why does feature branch validation fail when using spec-kit project structure?

Feature branch validation fails when the Git branch name does not match expected regular expression patterns or lacks a corresponding specs/ directory. The validation outputs messages indicating if the branch is invalid or not a feature branch.

Do I need a Git repository to validate spec-kit branch naming patterns?

Yes, you need a Git repository and a spec-kit project setup to validate branch naming patterns. The validation process checks the current Git branch name against regular expressions and verifies the corresponding spec directory exists.

What is the best way to enforce timestamped Git branch naming patterns?

The best way to enforce timestamped Git branch naming patterns is to apply regular expression validation to the current branch name. This verifies the naming convention is followed and confirms the matching spec directory exists under specs/.