skills.rest
nq-rdl
nq-rdlOFFICIAL
Explore all skills by this author →
GitHub

speckit-git-validate

Validate active Git branch names against sequential and timestamp patterns.

Updated Apr 3, 2026
Search Tags:#git#workflow#validation#branch#ci#feature-branch
One-click install
npx skills add https://github.com/nq-rdl/agent-skills --skill speckit-git-validate-nq-rdl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/nq-rdl/agent-skills/tree/main/.claude/skills/speckit-git-validate
Command: npx skills add https://github.com/nq-rdl/agent-skills --skill speckit-git-validate-nq-rdl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch naming inconsistencies hinder traceability and automation in feature development. This Skill validates that the current Git branch adheres to defined feature-branch naming patterns, enabling teams to enforce discipline and improve workflow automation.

Core Features & Use Cases

  • Validate the active branch name against the accepted patterns:
    • Sequential: ^[0-9]{3,}-
    • Timestamp: ^[0-9]{8}-[0-9]{6}-
  • Graceful fallback when Git is unavailable or not a repository, using SPECIFY_FEATURE if provided.
  • Output clear status messages indicating whether the current branch is valid and whether a related spec directory exists (for downstream tooling).

Quick Start

Run speckit-git-validate in your repository to verify that the active branch name matches the required feature-branch patterns.

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 my Git branch name against feature-branch naming patterns?▼

To validate a Git branch name, the Skill checks the active branch against sequential three-digit prefixes or timestamp YYYYMMDD-HHMMSS formats to ensure consistent feature tracking and automation.

What feature-branch naming patterns are supported for CI workflows?▼

Supported feature-branch naming patterns include sequential prefixes like three-digit numbers followed by a dash, and timestamp prefixes formatted as YYYYMMDD-HHMMSS- for CI workflow automation.

Can I validate a branch name if Git is unavailable or not a repository?▼

If Git is unavailable or not a repository, the Skill falls back to validating the SPECIFY_FEATURE environment variable, or it warns and skips validation entirely.

Why does feature-branch naming validation matter for local development?▼

Feature-branch naming validation matters because inconsistencies hinder traceability, spec linkage, and automation, making disciplined branch naming essential for reliable local development workflows.

Does the Skill report if a related spec directory exists for the branch?▼

Yes, the Skill outputs clear status messages indicating whether the current branch name is valid and whether a related spec directory exists for downstream tooling integration.

Do I need the git CLI installed to check branch naming conventions?▼

Yes, the git CLI must be available to identify and validate the active branch name, but the Skill gracefully falls back to the SPECIFY_FEATURE environment variable if the CLI is missing.

Related Skills

Explore More Software Engineering Skills→
joaquimscostajoaquimscosta
21

creating-branch

Create standardized Git feature branches with incrementing names.

Community
Advanced
d0whc3rd0whc3r
2

speckit-git-feature

Create and switch to a numbered git feature branch from a spec.

Community
Intermediate
arbazkhan971arbazkhan971
26

lint

Configure linters, formatters, pre-commit hooks, and CI enforcement across repositories.

Community
Advanced
brianpunzalanbrianpunzalan

speckit-git-validate

Validates Git branch names and ensures corresponding spec directories exist.

Community
Intermediate