speckit-git-validate

Validate current Git branch names against sequential and timestamped feature naming conventions.

Updated Mar 4, 2026

Search Tags:#git #validation #regex #ci #specs #development-workflow #branch-naming

Ready to run

npx skills add https://github.com/kerolos-saaid/refranario --skill speckit-git-validate-kerolos-saaid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/kerolos-saaid/refranario/tree/main/.agents/skills/speckit-git-validate
Command: npx skills add https://github.com/kerolos-saaid/refranario --skill speckit-git-validate-kerolos-saaid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle with inconsistent feature branch naming, leading to merge conflicts, unclear history, and reduced automation reliability. By validating the current branch against established patterns, this skill enforces discipline and accelerates review workflows.

Core Features & Use Cases

Validates sequential feature prefixes like 001-feature and 042-bugfix to ensure consistent ordering in CI dashboards.
Validates timestamped branches like 20260319-143022-feature-name to support time-based traceability.
Gracefully degrades in non-Git environments by issuing warnings and can verify the existence of corresponding specs under specs/ when applicable.

Quick Start

Run the speckit-git-validate tool to verify the current 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 validate Git branch naming conventions in CI pipelines?▼

Validating Git branch naming conventions in CI pipelines checks the current branch against predefined patterns like sequential prefixes or timestamps. This skill detects Git presence, verifies feature branch formats, and checks for spec directories under specs/ when applicable.

What feature branch naming patterns are supported for development workflows?▼

Supported feature branch naming patterns include sequential prefixes like 001-feature and timestamp-based names like 20260319-143022-feature-name. These patterns ensure consistent ordering in CI dashboards and support time-based traceability for development workflows.

Does branch name validation work in non-Git environments?▼

Branch name validation gracefully degrades in non-Git environments by issuing warnings instead of failing. When Git is unavailable or specs directories are missing, the validation detects the absence and proceeds without blocking the development workflow.

How do I enforce consistent feature branch naming with sequential prefixes?▼

Enforcing consistent feature branch naming with sequential prefixes involves validating branch names like 001-feature or 042-bugfix against established patterns. This discipline accelerates review workflows and ensures reliable automation by preventing inconsistent naming across teams.

Can I check for spec directories when validating a feature branch?▼

Checking for spec directories when validating a feature branch is supported under the specs/ path. When on a feature branch, the validation verifies the existence of corresponding specs, ensuring documentation aligns with branch naming conventions.

Why validate timestamp-based Git branch names?▼

Validating timestamp-based Git branch names like 20260319-143022-feature-name supports time-based traceability across development workflows. This pattern allows teams to track when branches were created, improving historical context and CI validation reliability.