skills.rest
luansilvadb
luansilvadbCOMMUNITY
Explore all skills by this author →
GitHub

speckit-git-validate

Validate active Git branch names against Spec Kit feature-branch conventions.

Updated Aug 23, 2026
Search Tags:#automation#git#workflow#validation#spec-kit#branch-naming
One-click install
npx skills add https://github.com/luansilvadb/divi-app --skill speckit-git-validate-luansilvadb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/luansilvadb/divi-app/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/luansilvadb/divi-app --skill speckit-git-validate-luansilvadb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that developers adhere to consistent feature-branch naming and automatically validates the current branch against the project's spec-kit conventions, reducing merge conflicts and quality risks.

Core Features & Use Cases

  • Validates the active branch name against sequential patterns like 001-feature-name and timestamp patterns like 20260319-143022-feature-name.
  • Provides graceful degradation when Git is unavailable or not in a repo, including SPECIFY_FEATURE fallback.
  • Reports clear status messages about branch validity and the existence of related spec directories under specs/ to guide workflow.

Quick Start

Run the validation check in a Spec Kit project directory and observe real-time feedback on the active branch.

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 in a Spec Kit project?▼

Git branch naming validation checks the active branch against sequential (000-) or timestamp (YYYYMMDD-HHMMSS-) formats. It reports clear status messages about branch validity and related spec directories under specs/ to guide your workflow.

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

Spec Kit workflows support sequential patterns like 001-feature-name and timestamp patterns like 20260319-143022-feature-name. Branch validation checks the active Git branch against these formats to ensure consistent feature-branch naming.

Can I validate branch names when Git is unavailable or not a repository?▼

When Git is unavailable or not in a repository, branch validation gracefully degrades by optionally using the SPECIFY_FEATURE variable as a fallback. It still reports clear status messages about branch validity and spec directory existence.

How do I check if my current Git branch matches sequential or timestamp formats?▼

Run the validation check in your Spec Kit project directory. It identifies the active Git branch and checks it against sequential (000- prefix) or timestamp (YYYYMMDD-HHMMSS- prefix) formats, triggering lookups in specs/ when appropriate.

Why should I enforce feature-branch naming conventions in Git?▼

Enforcing feature-branch naming ensures developers adhere to consistent formats and automatically validates branches against spec-kit conventions. This reduces merge conflicts and quality risks by maintaining strict sequential or timestamp patterns.

Related Skills

Explore More Software Engineering Skills→
Ab0umarAb0umar

speckit-git-validate

Validate Git branch names against feature-branch naming rules.

Community
Intermediate
sdk451sdk451

speckit-git-validate

Validate Git branch names against sequential or timestamped patterns and matching spec directories.

Community
Intermediate
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced
eavichayeavichay

git-validate

Validate Git branch names against sequential, timestamp, or custom patterns.

Community
Intermediate