speckit-git-feature

Create and switch to a numbered git feature branch from a spec.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-git-feature-d0whc3r
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-git-feature
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-git-feature-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive work of creating a correctly numbered git feature branch for a new specification, so teams can move from an idea to a working branch with consistent naming.

Core Features & Use Cases

  • Deterministic feature branch creation: Creates and switches to a new git feature branch for the given specification using the configured numbering strategy.
  • Sequential or timestamp numbering: Automatically chooses the next branch number using sequential mode or a timestamp-based mode depending on platform and configuration.
  • Environment override support: Respects an explicit GIT_BRANCH_NAME when provided, bypassing the normal prefix/suffix generation rules.

Quick Start

Tell the Skill to create a new feature branch using your specification description as input.

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?▼

Sequential numbering assigns the next logical integer to your feature branch, while timestamp numbering uses the current system time to generate a unique branch identifier, with the strategy selected via SKILL.md configuration.

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

Yes, you can override the generated git branch name by providing an explicit GIT_BRANCH_NAME environment variable, which bypasses the normal prefix and suffix generation rules completely during branch creation.

What is the best way to standardize feature branch naming for CI pipelines?▼

The best way to standardize feature branch naming for CI pipelines is using deterministic branch creation that applies a consistent numbering strategy, ensuring predictable feature numbering across your team's spec-kit workflow.

Does this branch creation tool require any external dependencies?▼

No, this branch creation tool does not require any external dependencies, operating entirely through a platform-specific create-new-feature script that outputs JSON results.

How do I configure the branch numbering strategy for my spec-kit workflow?▼

You configure the branch numbering strategy by guiding the selection process through SKILL.md, choosing between sequential mode or timestamp-based mode depending on your platform and project requirements.