skills.rest
ayehiaa
ayehiaaCOMMUNITY
Explore all skills by this author →
GitHub

speckit-git-validate

Validate Git feature branch names against sequential or timestamp patterns.

Updated May 2, 2026
Search Tags:#automation#git#specification#validation#branch naming#dev workflow#filesystem checks
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill speckit-git-validate-ayehiaa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill speckit-git-validate-ayehiaa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent Git feature branch names by validating that the current branch matches the expected feature naming conventions, helping keep repositories organized and automations reliable.

Core Features & Use Cases

  • Feature branch pattern validation: Checks whether the current branch name follows either a sequential numeric prefix format or a timestamp-based format.
  • Spec directory existence check: Verifies that the corresponding spec directory exists under the expected specs/ prefix, ensuring the branch has the right supporting documentation.
  • Graceful fallback behavior: If Git is unavailable or the directory is not a Git repository, it can validate using the SPECIFY_FEATURE environment variable and otherwise skips with a warning.

Quick Start

Run speckit-git-validate on your current working directory to verify your branch name and confirm the matching specs/ directory exists.

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?▼

To validate Git feature branch naming conventions, run this Skill in your repository to check if the current branch name matches sequential or timestamp patterns and has a corresponding specs directory.

What happens if my Git branch name doesn't match the spec directory?▼

If your Git branch name doesn't match the spec directory, the validation produces a warning output indicating the branch name fails the required pattern or the supporting documentation is missing.

Can I validate branch naming rules without a Git repository?▼

Yes, you can validate branch naming rules without a Git repository by using the SPECIFY_FEATURE environment variable as a fallback, otherwise the validation skips with a warning.

What branch naming formats are supported for development workflows?▼

Supported branch naming formats for development workflows include sequential numeric prefixes and timestamp-based formats, ensuring branch names correctly map to their corresponding spec directories.

Why do branch naming rules need to map to specs directories?▼

Branch naming rules map to specs directories to ensure branches have the correct supporting documentation, keeping repositories organized and automations reliable for review and tooling consistency.

Related Skills

Explore More Software Engineering Skills→
joaquimscostajoaquimscosta
21

creating-branch

Create standardized Git feature branches with incrementing names.

Community
Advanced
reedomreedom

detect-kiro-specs

Detect modified Kiro specs in the current branch using git diff.

Community
Basic
brianpunzalanbrianpunzalan

speckit-git-feature

Create a git feature branch with sequential or timestamp numbering from a specification.

Community
Intermediate
youssif-mohamed1youssif-mohamed1
1

speckit-git-validate

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

Community
Basic