speckit-git-validate

Delegate Git branch validation to a Speckit source skill.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill speckit-git-validate-opensoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-validate
Source: https://github.com/opensoft/dartwing-ocr-pipeline/tree/main/plugins/speckit/skills/speckit-git-validate
Command: npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill speckit-git-validate-opensoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-git-validate provides a safe wrapper to perform Git branch validation by delegating to a source Speckit skill, ensuring consistent checks without duplicating logic.

Core Features & Use Cases

  • Delegates validation to a source skill while maintaining a clear command surface.
  • Forwards any trailing input after the command to the source skill for flexible use.
  • Ensures the source skill is executed exactly, including its own validation behavior.

Quick Start

Invoke /speckit.git.validate to run the Git-branch validation using the Speckit source skill.

Frequently Asked Questions about speckit-git-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Git branch validation in my development workflow?

Git branch validation is automated by invoking the command to route input through a Speckit-powered source skill, executing consistent branch naming checks without duplicating validation logic.

What does a Speckit wrapper do for Git branch naming checks?

A Speckit wrapper provides a safe command surface that delegates Git branch naming checks to a source skill, ensuring consistent validation behavior while forwarding any trailing input directly to that skill.

How do I run a Git branch validation command with trailing input?

To run Git branch validation with trailing input, invoke the validation command; the wrapper automatically forwards any arguments appended after the command to the underlying Speckit source skill for execution.

Can I enforce consistent Git branch naming without duplicating validation logic?

Yes, consistent Git branch naming is enforced by delegating to a source Speckit skill, which executes exactly with its own validation behavior, eliminating the need to duplicate logic across your workflow.

Does Git branch validation require any dependencies or additional components?

Git branch validation via the Speckit wrapper requires no additional dependencies or components, operating independently to route input and execute the source skill's validation behavior directly.