skills.rest
bdunnette
bdunnetteCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-git-feature

Create and switch to standardized git feature branches from specifications.

Updated May 28, 2026
Search Tags:#automation#git#workflow#branching#spec-kit#feature-branch
One-click install
npx skills add https://github.com/bdunnette/reaper --skill speckit-git-feature-bdunnette
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/bdunnette/reaper/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/bdunnette/reaper --skill speckit-git-feature-bdunnette

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and switch to a new git feature branch for the given specification; this command handles branch creation only — the spec directory and files are created by the core /speckit-specify workflow.

Core Features & Use Cases

  • Generates a feature branch named from the specification with either sequential or timestamp-based numbering.
  • Supports environment variable overrides to customize the branch name.
  • Gracefully handles missing Git by warning and skipping branch creation; suitable for non-Git workflows.

Quick Start

Provide a feature specification and optionally set GIT_BRANCH_NAME to override the generated branch, then run the speckit git feature command to create and switch to the new branch.

Frequently Asked Questions about speckit-git-feature

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

FAQPage Schema
How do I automate git feature branch creation for a specification?▼

Automate git feature branch creation by running a command that generates a branch named from your specification with sequential or timestamp-based numbering, then switches to it automatically. This ensures consistent naming across multiple specs.

Can I override the generated git feature branch name?▼

Yes, you can override the generated git feature branch name by setting the GIT_BRANCH_NAME environment variable before running the command, allowing you to customize branch naming outside the default sequential numbering.

What happens if Git is not installed when creating a feature branch?▼

If Git is not available, the workflow gracefully handles the missing dependency by warning the user and skipping branch creation, making it suitable for non-Git workflows that still require specification tracking.

Does the speckit git feature command create the spec directory and files?▼

No, the speckit git feature command handles branch creation only. The spec directory and files must be created beforehand by the core speckit-specify workflow before you switch to the new branch.

How does sequential branch numbering work for feature tracking?▼

Sequential branch numbering assigns incremental numbers to each new feature branch tied to a specification, ensuring reproducible feature tracking across multiple specs and maintaining consistent naming conventions throughout the workflow.

Related Skills

Explore More Software Engineering Skills→
ZainEldeen-Ashraf-Ibrahim-Ibrahim-SamakZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak

speckit-git-feature

Create and switch to numbered git feature branches with JSON output.

Community
Intermediate
JoeCP17JoeCP17
8

commit-push

Stage changes, create a conventional commit, and push to the remote branch.

Community
Intermediate
MicrockMicrock
322

spec-kit-skill

Generate structured feature specifications across seven constitution-driven development phases.

Community
Advanced
alansmelloalansmello

speckit-git-feature

Create and switch to a new numbered git feature branch.

Community
Intermediate