speckit-git-validate

Validate current Git branch names against feature-branch prefix patterns.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-git-validate-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-git-validate
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-git-validate-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce standardized feature branch naming by validating the current Git branch against configured patterns and alerting when deviations occur.

Core Features & Use Cases

  • Validation of the current branch name against sequential and timestamp prefix patterns used in feature development workflows.
  • Graceful handling of non-Git environments by suggesting a fallback when repository context is missing.
  • Use case: when enacting strict branch-naming policies to improve traceability and automation in CI pipelines.

Quick Start

Run the validation to confirm the current branch name matches the feature-branch 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 validate a Git branch name against feature-branch conventions?

To validate a Git branch name, run the Skill to check the current branch against configured feature-branch naming patterns using regex rules for sequential and timestamp prefixes, reporting deviations and verifying spec directory existence.

Does Git branch validation work outside a Git repository?

Git branch validation gracefully handles non-Git environments by consulting the SPECIFY_FEATURE environment variable as a fallback to identify the intended feature context when repository access is missing.

What branch naming patterns are supported for feature branch validation?

Feature branch validation supports two specific pattern types using regex checks: sequential prefixes and timestamp prefixes, ensuring standard feature-branch naming conventions are strictly followed for workflow traceability.

How do I enforce strict branch-naming policies in a CI pipeline?

Enforce strict branch-naming policies in CI pipelines by applying this validation step to verify branch names against defined patterns, alerting on deviations to improve automation and traceability.

What happens if my feature branch name does not match the expected pattern?

If a feature branch name does not match the expected pattern, the validation reports the deviation, alerting teams to the naming inconsistency and verifying whether a corresponding spec directory exists.

Why validate feature branch names before merging code?

Validating feature branch names before merging ensures standard naming conventions are followed, improving project traceability and enabling reliable automation in CI pipelines by matching branches to spec directories.