speckit-git-validate

Validate Git branch names against spec-kit naming conventions.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Yangeok/i-cherri --skill speckit-git-validate-yangeok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/Yangeok/i-cherri/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/Yangeok/i-cherri --skill speckit-git-validate-yangeok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unit helps developers maintain consistent Git branch naming conventions, simplifying code organization and collaboration.

Core Features & Use Cases

  • Branch Naming Validation: Checks if the current Git branch name follows the specified naming conventions.
  • Compatibility Check: Ensures the presence of a .specify/ directory for compatibility with spec-kit project structures.
  • Graceful Degradation: Provides fallbacks and warnings if Git is not available or if the repository structure does not match expectations.

Quick Start

Run the speckit-git-validate skill to check 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 branch naming conventions in a spec-kit project?

You can validate Git branch naming conventions by running a check against your current branch name to ensure it follows specified rules for spec-kit project structures.

What happens if my Git repository lacks the .specify directory?

If the .specify directory is missing, the validation provides graceful degradation by issuing warnings and fallbacks rather than failing, ensuring compatibility with non-standard environments.

Do I need Git and spec-kit installed to check branch naming structures?

Yes, you need Git and spec-kit installed because the validation process requires them to perform checks on branch names and the underlying directory structure.

Can I check branch naming compatibility for non-standard spec-kit environments?

Yes, you can check branch naming compatibility in non-standard environments because the validation includes graceful degradation to provide fallbacks and warnings when repository structures do not match expectations.

Why is consistent Git branch naming validation important for code organization?

Git branch naming validation is important because it helps developers maintain consistent conventions, which simplifies code organization and collaboration across the project structure.