speckit-git-validate

Validate Git branch names against spec-kit naming conventions.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/TKlerx/webapp-template --skill speckit-git-validate-tklerx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/TKlerx/webapp-template/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/TKlerx/webapp-template --skill speckit-git-validate-tklerx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of maintaining consistent Git branch naming conventions, ensuring better organization and readability within a repository.

Core Features & Use Cases

  • Branch Naming Validation: Validates current branch naming against standard conventions.
  • Compatibility Check: Ensures compatibility with spec-kit project structure.
  • Quick Feedback: Provides immediate feedback on whether the current branch name is correct or needs to be corrected.

Quick Start

Validate your current Git branch with the speckit-git-validate skill.

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 in a spec-kit project?

To validate Git branch naming conventions, you can check the current branch name against expected sequential or timestamp formats to ensure it adheres to spec-kit project structure rules. This provides immediate feedback on whether the branch name is correct.

What branch naming patterns are compatible with a spec-kit project structure?

Spec-kit project structure compatible branch naming patterns include sequential formats and timestamp formats. The validation process checks for adherence to these specific patterns to maintain repository organization and readability.

How do I check if my spec directories are correctly named for my current Git branch?

To check if spec directories are correctly named, validate the current Git branch against the spec-kit project structure. This ensures that required spec directories are present and correctly named according to project conventions.

Does Git branch validation work without any external dependencies?

Git branch validation operates without external dependencies to check branch naming conventions. It directly analyzes the branch name pattern and verifies spec directory presence within the spec-kit project structure.

Why is my Git branch name failing spec-kit validation?

Git branch name validation fails when the branch name does not adhere to the required sequential or timestamp formats, or when the spec-kit project structure lacks correctly named spec directories. Immediate feedback identifies the specific naming issue.

What is the best way to enforce consistent Git feature branch naming?

The best way to enforce consistent Git feature branch naming is to validate branch names against standard conventions before integration. This ensures compatibility with the spec-kit project structure and maintains repository organization.