speckit-git-feature

Create and switch to a numbered Git feature branch from a specification.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/duonghuan2122000/sora-piggy --skill speckit-git-feature-duonghuan2122000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/duonghuan2122000/sora-piggy/tree/main/.claude/skills/speckit-git-feature
Command: npx skills add https://github.com/duonghuan2122000/sora-piggy --skill speckit-git-feature-duonghuan2122000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a Git feature branch based on a given specification, handling automatic sequential or timestamp-based numbering to streamline feature development.

Core Features & Use Cases

  • Branch creation and switch: generates a properly named feature branch and checks it out.
  • Flexible numbering: supports sequential by default and timestamp-based naming when configured.
  • Environment override: if GIT_BRANCH_NAME is provided, uses it directly, bypassing numbering.

Quick Start

Create a new feature branch for the provided specification, using sequential numbering by default, with an optional GIT_BRANCH_NAME override.

Frequently Asked Questions about speckit-git-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically create and switch to a Git feature branch for a new spec?

To create a Git feature branch for a specification, the skill generates a properly named branch using sequential or timestamp-based numbering and automatically checks it out, returning the branch name and number.

What is the default naming convention used when generating a feature branch?

The default naming convention for feature branch creation uses sequential numbering. You can configure timestamp-based numbering as an alternative mode to manage branch generation.

Can I override the automatic numbering and use a custom Git branch name?

Yes, you can bypass automatic numbering by providing a GIT_BRANCH_NAME environment override. When provided, the skill uses this custom name directly for the feature branch.

Do I need an existing Git repository to generate a feature branch for my spec?

Yes, the skill validates that Git is available and a repository is present before applying the configured numbering mode and switching to the new feature branch.

What is the best way to streamline feature development workflow with Git branching?

Automating feature branch creation with sequential or timestamp-based numbering streamlines feature development. This approach generates properly named branches and automatically switches to them.