speckit-branch-convention-validate

To validate git branch naming conventions, this skill loads patterns from the .specify/branch-convention.yml file, enumerates feature branches, and reports compliance or naming violations. It checks structure, type prefixes, sequence formatting, length, and ticket formats.

Enforcing compliance for feature branches and spec folders involves loading configured folder and branch patterns, pairing the directories with branches, and generating a readout of compliant and non-compliant items with actionable remediation guidance.

Yes, you can check spec folder naming patterns by loading the folder_pattern and token rules from the .specify/branch-convention.yml configuration file. The skill validates directory names against these extracted rules and reports violations.

Yes, this branch validation skill works without external dependencies. It operates independently by directly loading configuration from .specify/branch-convention.yml and enumerating existing git branches and spec-kit directories to check compliance.

Git branch names fail sequence formatting and ticket format checks when they do not match the configured type prefixes, length constraints, or ticket patterns defined in the .specify/branch-convention.yml file. The skill generates a report detailing these specific violations.

To get a compliance report for spec-kit branch naming violations, run the skill to evaluate paired branches and spec folders against configured patterns. It outputs a readout identifying non-compliant items and providing remediation guidance.