speckit-git-feature

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

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/BOUROUIS-MOHAMED/monclub_access_python --skill speckit-git-feature-bourouis-mohamed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/BOUROUIS-MOHAMED/monclub_access_python/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/BOUROUIS-MOHAMED/monclub_access_python --skill speckit-git-feature-bourouis-mohamed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and manages Git feature branches for a given specification, ensuring consistent naming and quick setup by delegating the actual spec creation to the core speck kit workflow.

Core Features & Use Cases

  • Create and switch to a new git feature branch for the given specification.
  • Branch naming supports sequential or timestamp numbering and accepts an explicit override via the GIT_BRANCH_NAME environment variable.
  • Validates context (Git availability and repository presence) and exposes BRANCH_NAME and FEATURE_NUM for downstream tooling.

Quick Start

Supply a specification to create and switch to the new feature 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 with consistent naming?

Git feature branch creation is automated by generating and switching to a new branch for a given specification. It enforces consistent naming conventions using sequential or timestamp-based numbering to maintain project organization.

Can I set an explicit Git branch name instead of using auto numbering?

You can set an explicit Git branch name by defining the GIT_BRANCH_NAME environment variable. When provided, this variable overrides the default sequential or timestamp-based auto-numbering logic for the feature branch.

How do I validate Git availability and repository context before branching?

Validating Git availability and repository context happens automatically before creating a feature branch. The process checks for an active Git repository to ensure branch creation and switching will succeed without context errors.

What downstream variables are available after creating a feature branch?

After creating a feature branch, the process exposes BRANCH_NAME and FEATURE_NUM variables. These outputs allow downstream tooling and automation scripts to reference the exact branch name and feature number for subsequent tasks.

Does this feature branch workflow support timestamp-based numbering?

Feature branch creation supports timestamp-based numbering as an alternative to sequential numbering. This mode generates branch names using current timestamps, useful for tracking exact creation times in version control workflows.

What is the best way to integrate feature branch creation into a spec-driven workflow?

The best way to integrate feature branch creation into a spec-driven workflow is passing a specification to the process. It delegates spec creation to the core workflow while handling branch creation, switching, and numbering automatically.