speckit-git-validate

Validate active Git branch names against feature-branch naming conventions.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/smile95137a/kuji-admin-web --skill speckit-git-validate-smile95137a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/smile95137a/kuji-admin-web/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/smile95137a/kuji-admin-web --skill speckit-git-validate-smile95137a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that the active Git branch name adheres to the repository's feature-branch naming conventions, preventing drift and ensuring predictable development workflows.

Core Features & Use Cases

  • Checks the current branch name against predefined patterns for sequential (three-digit prefix) and timestamp formats.
  • Guides users to the corresponding specs directory under specs/ and reports whether it exists.
  • Provides graceful degradation when Git is unavailable, and supports an environment-based fallback for non-Git contexts.

Quick Start

Run the speckit-git-validate command in a Git-enabled repository to verify your current branch matches the 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 validate Git branch naming conventions automatically?▼

Git branch naming conventions are validated automatically by checking the active branch against predefined sequential and timestamp patterns. The tool detects format drift and reports whether a matching spec directory exists under specs/ to ensure predictable workflows.

What branch naming patterns are supported for feature-branch validation?▼

Feature-branch validation supports sequential formats using a three-digit prefix and timestamp formats. It evaluates the active branch name against these predefined patterns to ensure adherence to repository conventions.

Does Git branch validation work without Git installed?▼

Git branch validation provides graceful degradation when Git is unavailable. It supports an environment-based fallback for non-Git contexts to continue validating branch naming conventions without a direct Git dependency.

Can I use feature-branch validation with a .specify project structure?▼

Feature-branch validation ensures compatibility with the .specify/ project structure. It guides users to the corresponding specs directory under specs/ and reports whether that matching directory currently exists.

Why does feature-branch naming validation fail for my Git branch?▼

Feature-branch naming validation fails when the active Git branch name does not match the sequential three-digit prefix or timestamp format. Ensure your branch name adheres to these predefined repository patterns to pass validation.