speckit-git-feature

Create a Git feature branch and output BRANCH_NAME and FEATURE_NUM.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of Git feature branches for a given specification, ensuring consistent naming and isolation of work.

Core Features & Use Cases

  • Automatic branch naming using a short, meaningful name derived from the feature description (with sequential or timestamp mode).
  • Supports sequential or timestamp-based numbering as configured.
  • Graceful handling when Git is unavailable, emitting BRANCH_NAME and FEATURE_NUM anyway for downstream tooling.

Quick Start

Create a new feature branch for the current specification.

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 with consistent naming?

You can automate Git feature branch creation by using a specification to derive a short, meaningful name. The skill outputs the branch name and feature number automatically, ensuring consistent naming and work isolation.

Can I create a Git feature branch even when Git is not available?

Yes, you can create a Git feature branch without Git available. The skill handles this gracefully by still emitting the branch name and feature number outputs for any downstream automation tooling.

How does feature branch numbering work in automated workflows?

Feature branch numbering defaults to sequential mode but can be configured. Alternatively, you can use timestamp-based numbering to control how branch names are generated for your specifications.

Do I need a specific Git environment to generate feature branches from specifications?

You need a Git-enabled environment to fully automate feature branch creation from a specification. However, the skill gracefully handles environments without Git by still outputting branch names for downstream tools.

What is the best way to isolate work when creating feature branches?

The best way to isolate work is to generate feature branches with consistent naming derived from a specification. This ensures sequential or timestamp-based numbering and outputs variables for downstream automation.