speckit-git-feature

Creates a numbered git feature branch for spec-kit specification workflows.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-git-feature-alkampfergit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/alkampfergit/cisharpai/tree/main/.claude/skills/speckit-git-feature
Command: npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-git-feature-alkampfergit

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. This Skill automates branch creation with sequential or timestamp-based numbering, removing manual naming decisions and keeping branch conventions uniform across the 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. - Flexible Numbering Modes: Supports sequential numbering (e.g., 003-user-auth) or timestamp prefixes (e.g., 20260319-143022-user-auth), configured via .specify/extensions/git/git-config.yml. - 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. - Use Case: A developer starting work on a new authentication feature invokes the skill with a description, and it creates the branch 004-add-user-auth, returning BRANCH_NAME and FEATURE_NUM as JSON for downstream spec-kit commands. ## Quick Start Ask the assistant to create a new feature branch for your specification, for example by saying create a feature branch for adding user authentication with OAuth2 support.

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

Invoke the skill with a feature description and it runs the create-new-feature script, generating a short name and creating the branch automatically. The script returns BRANCH_NAME and FEATURE_NUM as JSON for use by later spec-kit commands.

How does spec-kit branch numbering work?▼

Branch numbering is read from .specify/extensions/git/git-config.yml, falling back to .specify/init-options.json, and defaults to sequential. Sequential mode produces names like 003-user-auth, while 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 to use an exact branch name. This bypasses 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 a warning that no git repository was detected. The script still outputs BRANCH_NAME and FEATURE_NUM so the calling workflow can continue referencing them.

Does the skill create the specification files too?▼

No, this skill handles branch creation only. The spec directory and specification files are created separately by the core /speckit-specify workflow.