speckit-git-feature

Creates and switches to a Git feature branch for a specification with optional numbering and outputs BRANCH_NAME and FEATURE_NUM.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/vZulin/overlay-clock-timer --skill speckit-git-feature-vzulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/vZulin/overlay-clock-timer/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/vZulin/overlay-clock-timer --skill speckit-git-feature-vzulin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and switch to a new git feature branch for a given specification, ensuring consistent naming and optional numbering.

Core Features & Use Cases

  • Create and switch to a new feature branch for a specified spec.
  • Support sequential or timestamp-based branch numbering.
  • Override branch name using GIT_BRANCH_NAME environment variable.
  • Output BRANCH_NAME and FEATURE_NUM for downstream automation.

Quick Start

Create a new feature branch for a given specification using sequential numbering by default.

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 automatically create a Git feature branch, this skill creates and switches to a new branch for a given specification, ensuring consistent naming and optional sequential or timestamp-based numbering.

Can I use a custom naming convention when creating a Git feature branch?

Yes, you can override the automatic Git feature branch naming by setting the GIT_BRANCH_NAME environment variable to your desired custom branch name before execution.

How does sequential feature branch numbering work in Git automation?

Sequential feature branch numbering automatically increments a feature number for each new Git branch, outputting the FEATURE_NUM variable so downstream automation tasks can track the current sequence.

What is the best way to pass a generated Git branch name to downstream CI/CD automation?

The best way to pass a generated Git branch name to downstream automation is by using the BRANCH_NAME output variable provided after the feature branch is created and switched to.

Does this Git branch automation support timestamp-based numbering?

Yes, this Git branch automation supports timestamp-based numbering as an alternative to sequential numbering, allowing you to generate unique feature branches based on the current time.