speckit-git-feature

Creates a numbered git feature branch from a specification description using spec-kit scripts.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-git-feature-sethdavis512
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/sethdavis512/iridium/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-git-feature-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a new feature in a spec-kit project, developers need a consistently named git branch tied to the specification workflow. Manually choosing branch numbers and names leads to collisions and inconsistency across a team. ## Core Features & Use Cases - Automated branch creation: Runs the spec-kit create-new-feature script (Bash or PowerShell) to create and switch to a new feature branch in one step. - Sequential or timestamp numbering: Reads branch_numbering configuration from .specify/extensions/git/git-config.yml or .specify/init-options.json to pick the numbering strategy. - Short-name generation and override: Derives a 2-4 word action-noun short name from the feature description, or honors an explicit GIT_BRANCH_NAME override. - Use Case: A developer types a feature description like "add OAuth2 login" and receives a branch such as 003-add-oauth2-login, with JSON output containing BRANCH_NAME and FEATURE_NUM for downstream spec-kit commands. ## Quick Start Create a new feature branch for adding user authentication to my spec-kit project.

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 feature branch in a spec-kit project?

Provide a feature description and the skill runs the create-new-feature script for your platform (Bash or PowerShell) with a generated short name. The script creates and switches to the branch and returns JSON containing BRANCH_NAME and FEATURE_NUM.

How does spec-kit branch numbering work?

Branch numbering is determined by the branch_numbering value in .specify/extensions/git/git-config.yml, falling back to .specify/init-options.json, and defaults to sequential. A timestamp mode produces names like 20260319-143022-user-auth instead of numeric prefixes.

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.

What happens if Git is not installed or the directory is not a repository?

Branch creation is skipped with the warning '[specify] Warning: Git repository not detected; skipped branch creation'. The script still outputs BRANCH_NAME and FEATURE_NUM so the calling workflow can continue referencing them.

Does this skill create the specification files too?

No, it handles branch creation only. The spec directory and specification files are created separately by the core /speckit-specify workflow, so this skill should run alongside or after that step.