speckit-git-feature

Create and switch to a new Git feature branch for a specification.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/sdk451/claude-gdrive --skill speckit-git-feature-sdk451
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/sdk451/claude-gdrive/tree/main/.cursor/skills/speckit-git-feature
Command: npx skills add https://github.com/sdk451/claude-gdrive --skill speckit-git-feature-sdk451

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers quickly create and switch to a new Git feature branch with consistent naming, reducing manual naming errors and coordination overhead.

Core Features & Use Cases

  • Create and switch to a new Git feature branch for a given specification.
  • Supports sequential or timestamp-based numbering for branch names.
  • Overrides via GIT_BRANCH_NAME to force a specific branch name, with consistent outputs BRANCH_NAME and FEATURE_NUM.
  • Determines branch numbering mode from configuration, with a safe default to sequential.

Quick Start

Create and switch to a new Git feature branch for the given specification using the speckit 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 automatically create and switch to a new Git feature branch?

To create and switch to a Git feature branch automatically, use the speckit workflow which handles branch creation and naming, reducing manual errors and coordination overhead.

Can I override the default naming convention when creating a Git feature branch?

Yes, you can override the automatic Git feature branch naming by setting the GIT_BRANCH_NAME variable to force a specific branch name while still outputting BRANCH_NAME and FEATURE_NUM.

What numbering formats does automated Git feature branch creation support?

Automated Git feature branch creation supports both sequential and timestamp-based numbering, determining the mode from configuration while safely defaulting to sequential numbering.

Do I need to manually create spec files before generating a Git feature branch?

No, you do not manually create spec files for branch generation; the spec directory and files are created by the core speckit.specify workflow, and this command handles branch creation only.

What are the requirements to automate Git feature branch naming?

To automate Git feature branch naming, Git must be available in your environment, and you need a configuration file to determine sequential or timestamp-based numbering modes.

Why does my automatic feature branch creation fail to find the spec directory?

Feature branch creation fails because it handles branch switching only; the spec directory and files must be created beforehand by the core speckit.specify workflow.