speckit-git-validate

Validate Git branch names against sequential or timestamp patterns and check spec directories.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/anishakode/Steward_AI --skill speckit-git-validate-anishakode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/anishakode/Steward_AI/tree/main/.cursor/skills/speckit-git-validate
Command: npx skills add https://github.com/anishakode/Steward_AI --skill speckit-git-validate-anishakode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers verify that their Git branch names conform to established feature branch naming standards, promoting consistency across teams.

Core Features & Use Cases

  • Branch Name Validation: Checks if the current Git branch matches sequential or timestamp patterns.
  • Spec Directory Check: Verifies the existence of corresponding specification directories based on branch prefixes.
  • Use Case: When working on multiple features, quickly confirm that branch names adhere to standards and linked specs exist to streamline development workflows.

Quick Start

Run the speckit-git-validate Skill to check your current branch and find associated specification directories.

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 for feature development?

You can validate git branch names by applying pattern matching for sequential and timestamp formats. This process checks the current branch against established feature branch naming conventions to ensure consistent development workflows and organized repository structures.

How does spec directory validation work with feature branches?

Spec directory validation performs directory existence checks based on branch prefixes. It verifies that corresponding specification directories are present in the structured repository layout, ensuring linked specs exist for organized feature development workflows.

Do I need Git CLI access to check feature branch naming standards?

Yes, Git CLI access is required to validate feature branch naming standards. The process also requires a structured repository layout to correctly verify branch patterns and perform spec directory existence checks.

What is the best way to ensure feature branches follow naming conventions?

The best way to ensure feature branches follow naming conventions is to automate validation using pattern matching for sequential and timestamp formats. This approach verifies branch names and checks for corresponding spec directories simultaneously.

Why does my feature branch validation fail when checking spec directories?

Feature branch validation may fail if the corresponding specification directory does not exist in the structured repository layout. The validation process checks directory existence based on branch prefixes, so missing directories will cause the check to fail.