speckit-git-feature

Creates numbered git feature branches for spec-kit projects using sequential or timestamp-based naming.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-git-feature-alienstro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/alienstro/mediapipe-scroll/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-git-feature-alienstro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit users need consistent, correctly numbered git feature branches so teams can work in parallel without manual naming mistakes.

Core Features & Use Cases

  • Deterministic feature-branch creation: Creates and switches to a new git feature branch for a given specification while relying on the core /speckit.specify workflow to create spec files.
  • Configurable branch numbering mode: Selects sequential or timestamp-based numbering by reading branch_numbering from .specify/extensions/git/git-config.yml (or .specify/init-options.json as a fallback).
  • Environment override support: Allows a provided GIT_BRANCH_NAME to bypass generated prefix/suffix logic and use the exact branch name.

Quick Start

Ask the skill to create a new feature branch from your feature description for the current spec-kit workspace.

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 numbered git feature branches for spec-kit projects?

To create numbered git feature branches for spec-kit projects, provide a feature description and the skill invokes the platform-appropriate script to generate and switch to a correctly named branch. It returns a JSON object containing the branch name and feature number.

Can I use a custom git branch name instead of the generated sequential or timestamp numbering?

Yes, you can use a custom git branch name by providing an explicit GIT_BRANCH_NAME value. This overrides the generated prefix and suffix logic, allowing the spec-kit workspace to use your exact branch name directly.

How does spec-kit determine whether to use sequential or timestamp-based branch numbering?

Spec-kit determines branch numbering mode by reading the branch_numbering setting from the .specify/extensions/git/git-config.yml file. If that file is absent, it falls back to checking .specify/init-options.json to select the correct numbering format.

Do I need to manually run git commands to create feature branches in a spec-kit workspace?

No, you do not need to manually run git commands to create feature branches in a spec-kit workspace. The skill automates the entire workflow by invoking the create-new-feature script exactly once based on your feature description.

What output does the spec-kit git feature branch creation process return?

The spec-kit git feature branch creation process returns a JSON object containing BRANCH_NAME and FEATURE_NUM. This deterministic output ensures teams can track parallel feature branches without manual naming mistakes.

Why do my spec-kit feature branches have inconsistent naming across different workspace configurations?

Inconsistent spec-kit feature branch naming occurs when workspace configurations differ in their branch_numbering settings. The skill resolves this by standardizing branch creation through reading .specify git configuration files to ensure deterministic naming.