speckit-git-validate

Validate Git branch names against Spec-Kit naming conventions.

80|21|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/alfredoperez/speckit-companion --skill speckit-git-validate-alfredoperez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/alfredoperez/speckit-companion/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/alfredoperez/speckit-companion --skill speckit-git-validate-alfredoperez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that Git feature branches adhere to specific naming conventions, preventing merge conflicts and improving code organization.

Core Features & Use Cases

  • Branch Naming Validation: Checks if the current Git branch name matches predefined patterns.
  • Spec Directory Existence: Verifies the existence of a corresponding spec directory for the branch.
  • Compatibility Check: Ensures the branch naming convention is compatible with the Spec-Kit project structure.

Quick Start

Run the speckit-git-validate skill to validate the naming of your current Git branch.

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, run the validation tool to check if your current branch name matches predefined patterns and requires a .specify/ directory. This ensures compatibility with Spec-Kit project structures and prevents merge conflicts.

Why does branch naming validation require a .specify directory?

Branch naming validation requires a .specify/ directory because it verifies the existence of corresponding spec directories for the branch. This compatibility check ensures the branch naming convention aligns with the Spec-Kit project structure.

Can I check if my Git feature branch matches predefined naming patterns automatically?

Yes, you can check if your Git feature branch matches predefined naming patterns automatically by running the validation skill. It checks the current branch name against expected patterns to improve code organization and prevent merge conflicts.

What is the best way to prevent merge conflicts with Git branch naming?

The best way to prevent merge conflicts with Git branch naming is to enforce specific naming conventions across feature branches. Validating branch names against predefined patterns ensures consistent code organization within Spec-Kit projects.

Does Git branch validation work without a Spec-Kit project structure?

No, Git branch validation does not work without a Spec-Kit project structure. The validation process specifically requires the presence of a .specify/ directory to verify corresponding spec directories and ensure branch naming compatibility.