speckit-git-validate

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

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/silvarojasdiegoarturo91/fluxbot-studio-ia --skill speckit-git-validate-silvarojasdiegoarturo91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/silvarojasdiegoarturo91/fluxbot-studio-ia/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/silvarojasdiegoarturo91/fluxbot-studio-ia --skill speckit-git-validate-silvarojasdiegoarturo91

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers verify that their current Git branch name follows established naming conventions, preventing naming errors and maintaining project consistency.

Core Features & Use Cases

  • Branch Validation: Checks if the current branch name conforms to sequential or timestamp patterns.
  • Spec Directory Check: Verifies the existence of corresponding spec directories based on branch prefixes.
  • Use Case: A team wants to ensure all feature branches are properly named and associated with specifications, reducing integration issues.

Quick Start

Use the speckit-git-validate skill to confirm your branch name matches the pattern and locate its spec directory.

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

You can validate Git branch naming conventions automatically by using a skill that checks if your current branch name conforms to sequential or timestamp patterns, preventing misclassification and maintaining project consistency.

Why do I need to link feature branches to spec directories?

Linking feature branches to spec directories ensures structured development workflows by verifying the existence of corresponding spec directories based on branch prefixes, reducing integration issues and maintaining project consistency.

Can I check if my current Git branch name follows established patterns?

Yes, you can check if your current Git branch name follows established patterns by validating it against sequential or timestamp conventions and confirming it has a corresponding spec directory.

What is the best way to ensure Git branch naming compliance in a team?

The best way to ensure Git branch naming compliance in a team is to validate branch names against sequential or timestamp patterns and verify their associated spec directories, reducing integration issues and avoiding naming errors.

Does branch validation work with timestamp and sequential naming patterns?

Branch validation works with both timestamp and sequential naming patterns, checking if the current branch name conforms to these established conventions and locating its corresponding spec directory.