skills.rest
miloswrath
miloswrathCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-git-validate

Validate Git branch names against feature-branch naming conventions.

Updated Apr 7, 2026
Search Tags:#automation#git#validation#branch#spec-kit#naming-conventions#feature-branches
One-click install
npx skills add https://github.com/miloswrath/iproj-final --skill speckit-git-validate-miloswrath
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/miloswrath/iproj-final/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/miloswrath/iproj-final --skill speckit-git-validate-miloswrath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce consistent Git branch naming to improve traceability and enable automated spec-kit validations in development workflows.

Core Features & Use Cases

  • Validates branch names against sequential prefixes (e.g., 001-feature) or timestamp prefixes (e.g., 20260319-143022-feature).
  • Reports whether the current branch name is compliant and indicates if a corresponding spec directory exists under specs/ when present.
  • Graceful degradation for environments without Git or in non-repo directories by leveraging a SPECIFY_FEATURE fallback as described in the compatibility notes.

Quick Start

Run speckit-git-validate in a Git-enabled project to verify that the active branch name matches allowed 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 enforce feature-branch naming conventions in Git?▼

To enforce feature-branch naming conventions in Git, validate the active branch name against sequential 3+ digit prefixes or timestamp-based prefixes to ensure traceability and spec-kit compatibility.

What Git branch naming patterns are valid for spec-kit validation?▼

Valid Git branch naming patterns for spec-kit validation include sequential 3+ digit prefixes like 001-feature and timestamp-based prefixes like 20260319-143022-feature.

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

To validate a Git branch name against a specs directory, run validation in your repository to check branch compliance and locate corresponding spec directories under specs/.

Does Git branch validation work outside a repository or without Git installed?▼

Git branch validation gracefully degrades outside repositories or without Git by leveraging a SPECIFY_FEATURE fallback, allowing validation checks to proceed in non-repo directories.

Why should I use timestamp-based prefixes for Git feature branches?▼

Timestamp-based prefixes for Git feature branches improve traceability by embedding chronological data directly into the branch name, enabling automated spec-kit validations in development workflows.

Related Skills

Explore More Software Engineering Skills→
elsa-workflowselsa-workflows
7.9k

speckit-git-feature

Create git feature branches with sequential or timestamp-based names.

Official
Intermediate
KamiJeongKamiJeong

speckit-git-validate

Validate Git branch names against sequential or timestamp feature patterns.

Community
Intermediate
nsheapsnsheaps
3

smart-commit-analyzer

Analyze git changes and create atomic, convention-compliant commit messages.

Community
Advanced
YangeokYangeok

speckit-git-validate

Validate Git branch names against spec-kit naming conventions.

Community
Basic