speckit-git-feature

Name: speckit-git-feature
Availability: InStock
Author: tykhoncode

Create a numbered Git feature branch and switch to it from a specification.

Updated May 3, 2026

Search Tags:#automation #git #branching #spec-kit #sequential numbering #feature workflow #timestamp numbering

Ready to run

npx skills add https://github.com/tykhoncode/dicekit --skill speckit-git-feature-tykhoncode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/tykhoncode/dicekit/tree/main/.claude/skills/speckit-git-feature
Command: npx skills add https://github.com/tykhoncode/dicekit --skill speckit-git-feature-tykhoncode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of manually creating consistent, correctly numbered Git feature branches for each new spec, saving time and reducing naming errors.

Core Features & Use Cases

Creates and switches feature branches with sequential or timestamp-based numbering for a given specification.
Respects overrides by passing through GIT_BRANCH_NAME when explicitly provided, bypassing auto prefix/suffix logic.
Selects numbering mode from repo config by reading branch_numbering from .specify/extensions/git/git-config.yml or .specify/init-options.json, defaulting to sequential.

Quick Start

Ask your AI to create a new feature branch for the following spec: "Add OAuth2 token refresh to prevent session expiry."

Frequently Asked Questions about speckit-git-feature

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

FAQPage Schema

How do I create a numbered Git feature branch automatically?▼

Yes, spec-kit supports timestamp-based branch numbering alongside sequential numbering. It reads the branch_numbering setting from .specify configuration files, defaulting to sequential if no explicit timestamp mode is configured.

Can I override the automatic branch naming with a custom Git branch name?▼

Yes, you can override the automatic naming by providing a GIT_BRANCH_NAME variable. When explicitly set, the tool bypasses the sequential or timestamp prefix logic and uses your custom branch name directly.

Do I need a specific Git worktree setup to use automated feature branch creation?▼

You need a Git repository with worktree verification enabled. The tool checks the existing Git work-tree state before invoking the Bash or PowerShell creation script to ensure branch switching operates correctly.

How does spec-kit integrate branch creation with existing feature planning workflows?▼

Spec-kit integrates branch creation by reading configuration from .specify infrastructure files like init-options.json. This connects the generated feature branch directly to your specification description for streamlined planning.

What are the limitations of using automated branch numbering for feature workflows?▼

A limitation is that automated branch numbering depends on local .specify configuration files being present and correctly formatted. Without proper branch_numbering settings, it defaults to sequential, which may conflict if timestamp naming is expected.