speckit-git-validate

Validate Git branch naming conventions and verify associated spec directories.

7.9k|1.5k|Updated Oct 1, 2018
One-click install
npx skills add https://github.com/elsa-workflows/elsa-core --skill speckit-git-validate-elsa-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/elsa-workflows/elsa-core/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/elsa-workflows/elsa-core --skill speckit-git-validate-elsa-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers verify that their current Git branch name conforms to organizational standards, reducing miscommunication and improving workflow consistency.

Core Features & Use Cases

  • Branch Naming Validation: Checks if the current branch name matches specific patterns for sequential or timestamp formats.
  • Spec Directory Verification: Confirms the existence of corresponding specification directories based on branch prefix.
  • Use Case: When managing multiple feature branches, ensure each branch follows the naming convention and has an associated spec directory for proper tracking and validation.

Quick Start

Use the speckit-git-validate skill to check if your current Git branch name complies with your project standards.

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 for a feature workflow?

Git branch naming validation checks if your current branch name matches specific patterns for sequential or timestamp formats, ensuring project consistency. It verifies branch structure to reduce miscommunication in feature branch management workflows.

What is a spec directory and how does it relate to version control branches?

A spec directory in version control stores specifications associated with a feature branch. Branch validation verifies the existence of these corresponding spec directories based on the branch prefix to maintain proper specification tracking and project organization.

Can I check if my current Git branch name complies with project standards automatically?

You can check Git branch name compliance by running a validation script that compares your current branch name against organizational standards. It confirms whether the branch follows the required sequential or timestamp naming patterns for proper tracking.

Do I need access to Git commands to validate branch structure and spec directories?

Yes, Git branch validation requires access to Git commands and the project directory structure. The validation process executes Git commands to retrieve the current branch name and verifies the associated spec directory exists in the file system.

What is the best way to maintain consistency across multiple feature branches?

The best way to maintain consistency across feature branches is enforcing branch naming conventions and spec directory verification. Validating that each branch matches sequential or timestamp patterns and has an associated spec directory ensures proper tracking and organizational standards.

Why does my Git branch validation fail when checking spec directories?

Git branch validation fails when the branch name does not match expected sequential or timestamp patterns, or when the associated spec directory is missing. The validator checks the branch prefix to confirm the corresponding specification directory exists in the project structure.