speckit-git-feature

Create a numbered git feature branch for Spec Kit projects.

Updated May 18, 2026
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-git-feature-kamijeong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-git-feature-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create a correctly numbered git feature branch without manually deciding the branch name or numbering scheme, reducing setup friction for Spec Kit workflows.

Core Features & Use Cases

  • Branch Creation: Creates and switches to a new feature branch for a spec-driven task.
  • Numbering Support: Handles sequential or timestamp-based branch naming based on repository configuration.
  • Environment Override: Honors an explicitly provided branch name when you need exact control.
  • Use Case: A project maintainer can quickly start a new lesson, curriculum, or workflow change on a standardized branch before drafting the spec.

Quick Start

Ask the skill to create a feature branch for your current spec using a short, descriptive feature name.

Frequently Asked Questions about speckit-git-feature

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

FAQPage Schema
How do I create a feature branch for a Spec Kit project without manual naming?

To create a feature branch for a Spec Kit project automatically, this skill generates a correctly numbered branch using sequential or timestamp-based naming and switches to it. This eliminates manual naming decisions and reduces setup friction for new specs.

What is the best way to standardize git feature branch naming for curriculum changes?

Standardizing git feature branch naming for curriculum changes is handled by applying repository workflow configurations to generate sequential or timestamp-based names. This ensures every new lesson or workflow change adheres to a consistent numbering scheme.

Do I need a specific directory structure to use Spec Kit branch numbering?

Yes, you need a Spec Kit directory structure and git availability to use Spec Kit branch numbering. The skill relies on this specific repository layout to handle branch-numbering configuration and correctly apply the sequential or timestamp-based naming scheme.

Can I override the automatic branch name with a custom environment variable?

Yes, you can override the automatic branch name by providing an explicit name via an environment variable override. This honors exact control over branch creation when the standard sequential or timestamp-based naming does not fit your specific workflow needs.

When should I use a timestamp-based branch name instead of sequential numbering?

You should use timestamp-based branch naming instead of sequential numbering when working in parallel workflows where conflicts might occur. The skill handles both configurations, applying the scheme defined in your repository to prevent numbering collisions.