speckit-git-feature

Create and switch to a Git feature branch with sequential or timestamp numbering.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/iltan987/jetadisyon --skill speckit-git-feature-iltan987
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/iltan987/jetadisyon/tree/main/.claude/skills/speckit-git-feature
Command: npx skills add https://github.com/iltan987/jetadisyon --skill speckit-git-feature-iltan987

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creating and naming a Git feature branch for a given specification, consolidating manual branching into a deterministic workflow with optional sequential or timestamp numbering.

Core Features & Use Cases

  • Create and switch to a new git feature branch for the given specification; the spec directory and files are created by the core speckit.specify workflow.
  • Honor a GIT_BRANCH_NAME environment override so the exact branch name is used, bypassing numbering logic.
  • Outputs BRANCH_NAME and FEATURE_NUM for downstream automation and supports graceful degradation when Git is unavailable.

Quick Start

Create and switch to a new git feature branch based on the specification description, using sequential or timestamp numbering as configured.

Frequently Asked Questions about speckit-git-feature

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

FAQPage Schema
How do I automatically create and switch to a Git feature branch?

Automated Git feature branch creation uses a deterministic workflow to derive the branch name from a specification, then executes Git commands to create and switch to the new branch automatically.

What is deterministic feature branch naming in Git workflows?

Deterministic feature branch naming generates consistent branch names by deriving them from specification configurations, applying optional sequential or timestamp numbering rather than relying on manual input.

Can I override the auto-generated Git branch name with a custom value?

Yes, setting the GIT_BRANCH_NAME environment variable specifies an exact branch name, bypassing the automatic sequential or timestamp numbering logic during branch creation.

Does automated feature branch creation work outside a Git repository?

The workflow gracefully degrades in non-repo environments, avoiding failures when Git is unavailable, but an active Git repository is required to actually create and switch branches.

How do I pass feature branch data to downstream automation tasks?

The workflow outputs BRANCH_NAME and FEATURE_NUM variables after branch creation, allowing downstream automation tasks to consume the exact branch name and feature number for subsequent pipeline steps.