skills.rest
B0yZ4kr14
B0yZ4kr14COMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-git-validate

Validate Git feature branch naming and spec directory mapping.

Updated Mar 16, 2026
Search Tags:#git#validation#conventions#spec-kit#branch naming#repository hygiene#spec directory
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-git-validate-b0yz4kr14
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/kimi-cli/.kimi/skills/speckit-git-validate
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-git-validate-b0yz4kr14

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted time and broken workflows caused by inconsistent feature branch names that no longer map cleanly to spec directories.

Core Features & Use Cases

  • Branch naming validation: Checks whether the current Git branch matches either a sequential numeric prefix or a timestamp-based prefix.
  • Spec-directory existence check: Verifies that a corresponding spec directory exists under the expected specs path for the extracted prefix.
  • Graceful fallback behavior: When Git is unavailable, it can validate a provided branch value via the SPECIFY_FEATURE environment variable.

Quick Start

Ask to validate your current feature branch name and confirm whether the corresponding spec 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 against spec directories?▼

You can validate Git feature branch naming conventions by checking that the current branch uses a sequential numeric or timestamp-based prefix, then verifying a matching specs/<prefix>-* directory exists for that derived prefix.

What happens to branch validation when Git is unavailable?▼

When Git is unavailable, branch validation falls back to checking a provided branch value supplied through the SPECIFY_FEATURE environment variable, extracting the prefix to confirm the spec directory mapping.

How does spec directory mapping work with sequential or timestamp-based branch names?▼

Spec directory mapping works by extracting the sequential numeric or timestamp-based prefix from the feature branch name and locating a corresponding specs/<prefix>-* directory under the expected specs path.

Can I check repository hygiene without installing additional dependencies?▼

Yes, you can check repository hygiene without dependencies because the validation operates directly on Git state or the SPECIFY_FEATURE fallback to enforce branch naming and spec directory alignment.

Why does my feature branch fail the spec-kit directory existence check?▼

A feature branch fails the spec-kit directory existence check when the prefix extracted from the branch name cannot find a matching specs/<prefix>-* directory, indicating broken workflow alignment.

Related Skills

Explore More Software Engineering Skills→
tykhoncodetykhoncode

speckit-git-validate

Validate Git feature branch names and matching spec directories.

Community
Intermediate
juvenaljuvenal
8

speckit-git-validate

Validate Git feature branch names against sequential or timestamp patterns.

Community
Intermediate
Ab0umarAb0umar

speckit-git-validate

Validate Git branch names against feature-branch naming rules.

Community
Intermediate
youssif-mohamed1youssif-mohamed1
1

speckit-git-validate

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

Community
Basic