speckit-git-feature

Creates a numbered git feature branch from a specification description.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually naming and numbering feature branches in spec-driven projects is inconsistent and error-prone. This Skill automates branch creation with sequential or timestamp-based numbering so every feature branch follows the project convention. ## Core Features & Use Cases - Automated Branch Numbering: Determines the next sequential number or timestamp prefix automatically by reading project configuration, with no manual --number flag needed. - Short Name Generation: Derives a concise 2-4 word action-noun branch slug from the feature description while preserving technical terms like OAuth2 or JWT. - Cross-Platform Scripts: Invokes Bash or PowerShell scripts that output structured JSON containing BRANCH_NAME and FEATURE_NUM. - Use Case: While running a spec-kit workflow, ask to create a branch for "add user authentication" and receive a branch like 003-add-user-auth created and checked out automatically. ## Quick Start Create a feature branch for the specification "add OAuth2 login flow" using the speckit git feature workflow.

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

Provide a feature description and the skill generates a 2-4 word short name, then runs the create-new-feature script which assigns the next sequential number automatically. The script outputs JSON with BRANCH_NAME and FEATURE_NUM.

How does sequential vs timestamp branch numbering work?▼

The numbering mode is read from .specify/extensions/git/git-config.yml first, then .specify/init-options.json for backward compatibility. If neither specifies branch_numbering, sequential numbering is used by default; timestamp mode produces prefixes like 20260319-143022.

Can I override the generated git branch name?▼

Yes, set the GIT_BRANCH_NAME environment variable before invoking the script. The exact value is used as the branch name, bypassing prefix and suffix generation, and the --short-name, --number, and --timestamp flags are ignored.

Does this work outside a git repository?▼

Branch creation is skipped with a warning when Git is unavailable or the directory is not a git repository. The script still outputs BRANCH_NAME and FEATURE_NUM so the calling workflow can continue referencing them.

What are the prerequisites for using this branch creation workflow?▼

The project must follow the spec-kit structure with a .specify directory containing the extension scripts. Git should be installed, and the skill only creates the branch; spec directories and files are created separately by the speckit-specify workflow.