speckit-git-validate

Validate Git feature branch names against predefined naming patterns.

128|7|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/PieroSierra/SecondBrain --skill speckit-git-validate-pierosierra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/PieroSierra/SecondBrain/tree/main/.claude/skills/speckit-git-validate
Command: npx skills add https://github.com/PieroSierra/SecondBrain --skill speckit-git-validate-pierosierra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a consistent and predictable feature branch naming convention in Git repositories, which is crucial for code organization and collaboration.

Core Features & Use Cases

  • Branch Naming Validation: Checks if the current Git branch name adheres to specified naming patterns.
  • Compatibility Check: Ensures the repository follows the spec-kit project structure.
  • Spec Directory Verification: Confirms the existence of the corresponding spec directory for the branch.

Quick Start

Run the command to validate the current branch's naming convention: speckit-git-validate.

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 feature branch naming conventions automatically?

You can validate Git feature branch naming conventions by running a validation command that checks the current branch name against predefined sequential or timestamp patterns. This ensures branch names follow predictable formats for better code organization.

Does branch naming validation work with spec-kit project structures?

Branch naming validation works with spec-kit project structures by requiring a .specify/ directory. The validator checks branch naming patterns and verifies the existence of the corresponding spec directory within the spec-kit structure.

What Git branch naming patterns can I enforce for feature branches?

You can enforce sequential or timestamp patterns for Git feature branch naming. The validation process checks the current branch name against these predefined patterns to maintain consistency across the repository.

Why does my branch validation fail when the spec directory is missing?

Branch validation fails when the spec directory is missing because the validator confirms the existence of the corresponding spec directory for the branch. A .specify/ directory is required for the validation to pass successfully.

Can I check if my current Git branch matches the required naming format?

You can check if your current Git branch matches the required naming format by running the validation command. It evaluates the branch name against sequential or timestamp patterns and verifies the corresponding spec directory exists.

What is the best way to maintain consistent Git branch naming in a team?

The best way to maintain consistent Git branch naming in a team is to use an automated validation tool that checks branch names against predefined patterns. This ensures all feature branches follow the same sequential or timestamp naming conventions.