skills.rest
tellbom
tellbomCOMMUNITY
Explore all skills by this author →
GitHub

speckit-git-validate

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

Updated Apr 13, 2026
Search Tags:#git#workflow#devops#validation#specs#branch-naming#feature-branch
One-click install
npx skills add https://github.com/tellbom/process --skill speckit-git-validate-tellbom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/tellbom/process/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/tellbom/process --skill speckit-git-validate-tellbom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This validation helps teams ensure that their current Git branch names follow the defined feature-branch conventions, reducing ambiguity and aligning work with specs.

Core Features & Use Cases

  • Detects whether you are on a feature branch and prints the outcome.
  • Validates branch names against sequential (e.g., 001-feature) or timestamp (e.g., 20260319-143022-feature) patterns.
  • Verifies the existence of a corresponding spec directory under specs/ when a matching prefix is found, enabling streamlined test/workflow mapping.
  • Gracefully degrades when Git is unavailable or not in a repository by offering a SPECIFY_FEATURE fallback.

Quick Start

Run this skill in your Git repository to verify that the current branch name matches the allowed patterns and locate the corresponding 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 enforce feature-branch naming conventions in a Git repository?▼

Feature-branch naming conventions are enforced by validating the active Git branch against predefined patterns, reducing ambiguity and aligning work with specs. The Skill detects your current branch and prints whether it conforms to sequential or timestamp naming rules.

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

Supported Git feature-branch naming patterns include sequential formats like 001-feature and timestamp formats like YYYYMMDD-HHMMSS-feature. The Skill validates active branches against these predefined patterns to ensure consistent naming.

How do I validate a Git branch name against a corresponding specs directory?▼

To validate a Git branch name against a specs directory, the Skill checks for the existence of a corresponding spec directory under specs/ when a matching sequential or timestamp prefix is found. This enables streamlined test and workflow mapping.

Can I validate branch naming without Git installed in my local environment?▼

You can validate branch naming without Git by using the SPECIFY_FEATURE fallback. When Git is unavailable or the directory is not a repository, the Skill gracefully degrades and offers this override to determine branch validity.

What happens if my current Git branch name does not match the expected feature-branch format?▼

If your current Git branch name does not match the expected feature-branch format, the Skill detects the mismatch and provides appropriate messaging. It evaluates the branch against sequential and timestamp patterns to determine validity.

Related Skills

Explore More Software Engineering Skills→
nq-rdlnq-rdl

speckit-git-validate

Validate active Git branch names against sequential and timestamp patterns.

Official
Intermediate
tykhoncodetykhoncode

speckit-git-validate

Validate Git feature branch names and matching spec directories.

Community
Intermediate
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate
iludeilude
8

git-workflow

Validate Git commits for secrets and enforce safe push rules.

Community
Intermediate