Agent skill

Speckit Git Validate

by kunstmusik in kunstmusik/blue

Validate current branch follows feature branch naming conventions

GPL-3.0Auto-check passedDevelopment

Install Speckit Git Validate

skills CLI
$ npx skills add kunstmusik/blue --skill speckit-git-validate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kunstmusik/blue speckit-git-validate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kunstmusik/blue.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/speckit-git-validate .claude/skills/speckit-git-validate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
speckit-git-validate
GitHub stars
154
Used in
5 other repos
Token cost
~489 tokens
SKILL.md length
201 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
GPL-3.0

At a glance

Validate current branch follows feature branch naming conventions

  • Works in 2 steps: Sequential: ^[0-9]{3,}- (e.g.,… → Timestamp: ^[0-9]{8}-[0-9]{6}- (e.g.,…
  • Tasks that involve Spec-driven development
  • SKILL.md covers Prerequisites, Validation Rules, Execution and Graceful Degradation
  • Calls git

What it does

Speckit Git Validate is an agent skill from kunstmusik/blue. Validate current branch follows feature branch naming conventions

Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires spec-kit project structure with .specify/ directory

It sits in Development, covering Spec-driven development and Git workflow. It works with Git. The repository describes itself as: Blue - An Integrated Music Environment. The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Spec-driven development
  • Tasks that involve Git workflow

Example prompts

  • “/speckit-git-validate”

Requirements

  • Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Sequential: ^[0-9]{3,}- (e.g., 001-feature-name, 042-fix-bug, 1000-big-feature)
  2. Timestamp: ^[0-9]{8}-[0-9]{6}- (e.g., 20260319-143022-feature-name)

What it can do on your machine

Read from SKILL.md and the folder at commit ab9862c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires spec-kit project structure with .specify/ directory

    From compatibility in the SKILL.md frontmatter.

Context cost

Speckit Git Validate loads about 489 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 201 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~489

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from kunstmusik/blue at commit ab9862c, republished under its GPL-3.0 licence (© kunstmusik). 201 words, ~489 tokens.

Download SKILL.mdSave it as .claude/skills/speckit-git-validate/SKILL.md (or your agent's skills folder).
name
speckit-git-validate
description
Validate current branch follows feature branch naming conventions
compatibility
Requires spec-kit project structure with .specify/ directory
metadata.author
spec-kit-core
metadata.source
extension:git

Git Validate Skill

Validate Feature Branch

Validate that the current Git branch follows the expected feature branch naming conventions.

Prerequisites

  • Check if Git is available by running git rev-parse --is-inside-work-tree 2>/dev/null
  • If Git is not available, output a warning and skip validation:
    [specify] Warning: Git repository not detected; skipped branch validation

Validation Rules

Get the current branch name:

bash
git rev-parse --abbrev-ref HEAD

The branch name must match one of these patterns:

  1. Sequential: ^[0-9]{3,}- (e.g., 001-feature-name, 042-fix-bug, 1000-big-feature)
  2. Timestamp: ^[0-9]{8}-[0-9]{6}- (e.g., 20260319-143022-feature-name)

Execution

If on a feature branch (matches either pattern):

  • Output: ✓ On feature branch: <branch-name>
  • Check if the corresponding spec directory exists under specs/:
    • For sequential branches, look for specs/<prefix>-* where prefix matches the numeric portion
    • For timestamp branches, look for specs/<prefix>-* where prefix matches the YYYYMMDD-HHMMSS portion
  • If spec directory exists: ✓ Spec directory found: <path>
  • If spec directory missing: ⚠ No spec directory found for prefix <prefix>

If NOT on a feature branch:

  • Output: ✗ Not on a feature branch. Current branch: <branch-name>
  • Output: Feature branches should be named like: 001-feature-name or 20260319-143022-feature-name

Graceful Degradation

If Git is not installed or the directory is not a Git repository:

  • Check the SPECIFY_FEATURE environment variable as a fallback
  • If set, validate that value against the naming patterns
  • If not set, skip validation with a warning

© kunstmusik, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/speckit-git-validate of kunstmusik/blue.

Open the folder on GitHubat commit ab9862c

Used in 5 other repositories

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in kunstmusik/blue, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Speckit Git Validate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Speckit Git Validate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Speckit Git Validate this skillkunstmusik/blue1545 repos~489Automated safety check: PassGPL-3.0
MoAI Worktree Managementmodu-ai/moai-adk1.2k—~3.9kAutomated safety check: PassApache-2.0
Speckit Git Featureopsmill/infrahub531—~638Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT

Similar skills

  • MoAI Worktree Management

    modu-ai/moai-adk

    Gives each SPEC its own Git worktree with a registry of active workspaces, base-branch sync and cleanup of merged ones, inside the MoAI-ADK workflow.

    1.2k GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Speckit Git Feature

    opsmill/infrahub

    Validate Jira/JPD ticket reference and create a feature branch

    531 GitHub stars~638 tokensUpdated today
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

More from kunstmusik/blue

All 16 skills in this repo
  • Speckit Taskstoissues

    kunstmusik/blue

    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

    154 GitHub starsUsed in 19 repos~2k tokens
    Auto-check passed
  • Speckit Analyze

    kunstmusik/blue

    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

    154 GitHub starsUsed in 18 repos~3k tokens
    Auto-check passed
  • Speckit Plan

    kunstmusik/blue

    Execute the implementation planning workflow using the plan template to generate design artifacts.

    154 GitHub starsUsed in 18 repos~2.1k tokens
    Auto-check passed
  • Speckit Specify

    kunstmusik/blue

    Create or update the feature specification from a natural language feature description.

    154 GitHub starsUsed in 18 repos~4.7k tokens
    Auto-check passed
  • Karpathy Coder

    kunstmusik/blue

    A skill your agent uses when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define…

    154 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Speckit Tasks

    kunstmusik/blue

    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

    154 GitHub starsUsed in 18 repos~3k tokens
    Auto-check passed

Works with

Categories

Questions about Speckit Git Validate

What does Speckit Git Validate do?

Validate current branch follows feature branch naming conventions. Speckit Git Validate is an agent skill from kunstmusik/blue.

When should I use Speckit Git Validate?

Speckit Git Validate fits situations like: tasks that involve Spec-driven development; tasks that involve Git workflow.

How do I install Speckit Git Validate in Claude Code?

Run `npx skills add kunstmusik/blue --skill speckit-git-validate -a claude-code`. Or copy the skill folder (.agents/skills/speckit-git-validate in kunstmusik/blue) into .claude/skills/speckit-git-validate in your project. Claude Code loads it when a task matches its description.

How do I install Speckit Git Validate in Codex?

Run `npx skills add kunstmusik/blue --skill speckit-git-validate -a codex`. Or copy the skill folder (.agents/skills/speckit-git-validate in kunstmusik/blue) into .agents/skills/speckit-git-validate in your project. Codex loads it when a task matches its description.

Can I use Speckit Git Validate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kunstmusik/blue --skill speckit-git-validate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/speckit-git-validate, .gemini/skills/speckit-git-validate, .github/skills/speckit-git-validate and .opencode/skills/speckit-git-validate in your project.

What does Speckit Git Validate need to run?

Going by SKILL.md and its folder, Speckit Git Validate needs the command-line tools its instructions call (git). Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory.

Does Speckit Git Validate access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Speckit Git Validate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Speckit Git Validate use?

Speckit Git Validate is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Speckit Git Validate use?

About 489 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Speckit Git Validate?

Skills that share tags, products or a category with Speckit Git Validate: MoAI Worktree Management (modu-ai/moai-adk, 1.2k stars), Speckit Git Feature (opsmill/infrahub, 531 stars), Finishing a Development Branch (obra/superpowers, 296k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Speckit Git Validate?

kunstmusik (a GitHub user) maintains it in kunstmusik/blue, which has 154 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 7, 2026.

Source: kunstmusik/blue on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.