speckit-git-validate

Validate Git branch names against sequential or timestamped naming patterns.

25|4|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Rubiss-Projects/spec-kit-ralph --skill speckit-git-validate-rubiss-projects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/Rubiss-Projects/spec-kit-ralph/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/Rubiss-Projects/spec-kit-ralph --skill speckit-git-validate-rubiss-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that your Git branches follow proper naming conventions, preventing confusion and facilitating collaboration in a team environment.

Core Features & Use Cases

  • Branch Naming Validation: Checks the current branch name against specified patterns.
  • Compatibility with Spec-Kit Projects: Designed to work within a Spec-Kit project structure.
  • Graceful Degradation: Handles cases where Git is not available by checking an environment variable for feature information.
  • Use Case: Before merging, ensure that the feature branch naming convention is followed to maintain code quality and team consistency.

Quick Start

Use the 'speckit-git-validate' Skill to validate the current branch's 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 before merging?

To validate Git branch naming conventions before merging, use this Skill to check the current branch name against specified sequential or timestamped patterns. It identifies compliance issues and outputs branch validity to maintain code quality and team consistency.

What branch naming patterns are supported in a spec-kit environment?

In a spec-kit environment, the supported branch naming patterns are sequential numeric and timestamped formats. The Skill checks if the current branch follows one of these two specific patterns to ensure proper project naming conventions are met.

Can I check branch naming conventions if Git is not installed?

If Git is not installed, you can still check branch naming conventions through graceful degradation. The Skill falls back to checking an environment variable for feature information to validate the branch naming pattern.

Why do I need to enforce branch naming conventions in my codebase?

You need to enforce branch naming conventions to prevent confusion and facilitate collaboration in a team environment. Validating feature branches before merging ensures code quality and maintains team consistency across the project.

Does this branch validation Skill work outside of spec-kit projects?

This branch validation Skill is specifically designed to work within a spec-kit project structure. It validates Git branch naming against patterns tailored for the spec-kit environment to ensure project-specific conventions are followed.