speckit-git-feature

Create and checkout a Git feature branch from a specification.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-git-feature-omerkllm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/omerkllm/edris-antigravity/tree/main/.agent/skills/speckit-git-feature
Command: npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-git-feature-omerkllm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and switch to a new git feature branch for the given specification, ensuring the branch naming follows a deterministic strategy and the spec directory is produced by the core workflow.

Core Features & Use Cases

  • Branch creation only: Creates and switches to a new feature branch; the spec directory and files are produced by the core workflow.
  • Naming strategies: Supports sequential and timestamp-based numbering, and honors an explicit GIT_BRANCH_NAME override when provided.
  • Integration-ready: Outputs BRANCH_NAME and FEATURE_NUM for downstream tooling and automation.

Quick Start

Provide a feature specification and run the speckit workflow to generate and switch to a 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 automate git feature branch creation from a specification?

To automate git feature branch creation, this Skill creates and switches to a new branch directly from a provided feature specification. It applies deterministic naming strategies and outputs the generated branch name for downstream tooling.

Can I override the git branch naming strategy with a specific name?

Yes, you can override the git branch naming strategy by providing an explicit GIT_BRANCH_NAME value. When provided, the feature branch creation process honors this override instead of using sequential or timestamp-based numbering.

How does deterministic feature branch naming work with sequential and timestamp numbering?

Deterministic feature branch naming works by applying either sequential or timestamp-based numbering to generate consistent branch names. This ensures reproducible tracking and outputs a FEATURE_NUM alongside the final BRANCH_NAME for automation workflows.

Do I need Git installed locally to use an automated feature branch workflow?

Yes, you need Git installed locally because the workflow performs prerequisite checks for Git availability before executing. Ensuring Git is available allows the automation to successfully create and check out the new feature branch.

What outputs does an automated feature branch generator provide for CI/CD pipelines?

An automated feature branch generator provides BRANCH_NAME and FEATURE_NUM as outputs for CI/CD pipelines. These variables allow downstream tooling and automation scripts to reference the newly created branch deterministically.

Does the feature branch creation process also generate the spec directory and files?

No, the feature branch creation process does not generate the spec directory and files itself. It focuses strictly on creating and switching to the branch, while the core workflow handles producing the specification directory and files.