speckit-git-feature

Create and switch to a Git feature branch with deterministic numbering.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and switching to a new Git feature branch using deterministic, numbered naming to enforce consistency across teams and workflows.

Core Features & Use Cases

  • Create and switch to a new feature branch based on a concise description.
  • Support sequential or timestamp-based numbering, with optional user overrides.
  • Integrate with CI/CD pipelines to ensure standardized branch naming conventions.

Quick Start

Provide the feature description and any overrides, and let speckit 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?

You can automate git feature branch creation by providing a concise description to generate deterministic, numbered branch names. This enforces naming consistency across local development and CI workflows.

Can I use a custom branch name instead of automatic sequential numbering?

Yes, you can bypass automatic numbering by setting the GIT_BRANCH_NAME environment variable. This allows you to enforce custom naming overrides for specific local or CI workflows.

Does this branch naming tool support timestamp-based numbering?

Yes, the feature branch automation supports both sequential and timestamp-based numbering. This ensures deterministic branch names that integrate smoothly into CI/CD pipelines.

What is the best way to standardize feature branch names in CI workflows?

Standardizing feature branch names in CI workflows is best achieved by automating branch creation with deterministic numbering and validating inputs. This outputs a usable branch name for downstream processes.