skills.rest
opsmill
opsmillOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-git-validate

Validate Git feature-branch names against sequential or timestamp patterns.

9|4|Updated May 13, 2025
Search Tags:#git#workflow#validation#branch#feature-branch
One-click install
npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-git-validate-opsmill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/opsmill/infrahub-mcp/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-git-validate-opsmill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that the current Git branch name adheres to predefined feature-branch naming patterns.

Core Features & Use Cases

  • Branch name validation against patterns: sequential like 001-feature-name and timestamp like 20260319-143022-feature-name.
  • Optional spec directory check under specs/ to align with feature prefixes.
  • Graceful fallback via SPECIFY_FEATURE environment variable if Git is unavailable or not a repo.

Quick Start

Run the speckit-git-validate skill to confirm the current Git branch follows the designated feature-branch naming rules.

Frequently Asked Questions about speckit-git-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce feature-branch naming conventions in a Git repository?▼

You can enforce feature-branch naming by validating the current Git branch against predefined sequential patterns like 001-feature-name or timestamp formats like 20260319-143022-feature-name.

What Git branch naming patterns are supported for feature branches?▼

Supported feature-branch naming patterns include sequential prefixes matching ^[0-9]{3,}- and timestamp prefixes matching ^[0-9]{8}-[0-9]{6}-, ensuring standardized branch identification.

Does Git branch validation work in CI workflows without a local repository?▼

Git branch validation works in CI workflows by falling back to the SPECIFY_FEATURE environment variable when Git is unavailable or the directory is not a recognized repository.

How do I check if a spec directory exists for my current Git feature branch?▼

You can check for a matching spec directory by validating that a corresponding folder exists under specs/, aligning your feature branch prefix with the required specification structure.

Related Skills

Explore More Software Engineering Skills→
joaquimscostajoaquimscosta
21

creating-branch

Create standardized Git feature branches with incrementing names.

Community
Advanced
alienstroalienstro

speckit-specify

Generate structured feature specifications from natural-language descriptions.

Community
Advanced
the-perfect-developerthe-perfect-developer
11

git-hooks

Automate local Git workflow validation with pre-commit checks and push triggers.

Community
Advanced
pkuppenspkuppens

plan-branch-strategy

Create and switch to a planning feature branch with naming validation.

Community
Intermediate