speckit-git-feature

Create and switch to a new Git feature branch from a specification.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/smile95137a/kuji-admin-web --skill speckit-git-feature-smile95137a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/smile95137a/kuji-admin-web/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/smile95137a/kuji-admin-web --skill speckit-git-feature-smile95137a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and switch to a new git feature branch for the given specification. This command handles branch creation only — the spec directory and files are created by the core /speckit.specify workflow.

Core Features & Use Cases

  • Create and switch to a new feature branch based on the specification description.
  • Supports sequential or timestamp-based numbering to ensure unique branches.
  • Honors GIT_BRANCH_NAME overrides to bypass automatic naming when provided.
  • Validates Git availability and config-driven branch numbering mode before execution.

Quick Start

Provide a feature description to generate and switch to the new feature branch.

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 and switch to a new git feature branch automatically?▼

Use this command with a feature description to generate and switch to a new git branch automatically, validating Git availability and reading branch_numbering configuration before execution.

How does automatic feature branch numbering work in version control workflows?▼

Automatic feature branch numbering reads branch_numbering configuration to support sequential or timestamp-based numbering, generating unique branches without requiring manual numbering.

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

Yes, you can bypass automatic naming by providing a GIT_BRANCH_NAME override, which replaces the generated descriptive branch name with your custom value.

Does this branching workflow create the spec directory and feature files?▼

No, this handles branch creation only and defers actual spec directory and file creation to the core speckit.specify workflow within the feature development process.

What do I need to set up before using automated git feature branching?▼

You need Git available in your environment and a configured branch_numbering setting to determine whether sequential or timestamp-based numbering is applied to your branches.

What are the limitations of using automated branch creation for feature development?▼

A limitation is that it focuses solely on branch creation and switching, deferring spec file creation to the core workflow and requiring pre-configured branch_numbering settings to function correctly.