speckit-git-feature

Create and switch to a new numbered git feature branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and switch to a new git feature branch with sequential or timestamp numbering.

Core Features & Use Cases

  • Enforces naming conventions for feature branches.
  • Supports environment overrides for custom branch names.
  • Works across Git workflows with optional numbering schemes (sequential or timestamp).

Quick Start

Create and switch to a new feature branch using the configured naming scheme.

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 git feature branch with sequential numbering?

To create a git feature branch with sequential numbering, use a Skill that enforces a configurable naming scheme and handles optional numbering modes via Git tooling. It automatically creates and switches to the newly numbered branch.

What's the best way to enforce naming conventions for feature branches across multiple teams?

Enforcing naming conventions for feature branches across multiple teams requires a workflow tool that applies a configurable naming scheme and supports environment overrides for custom branch names. This ensures disciplined branching for features and experiments.

Can I use timestamp-based numbering instead of sequential numbers for git branches?

Yes, you can use timestamp-based numbering for git branches. The Skill handles optional numbering schemes, allowing you to choose between sequential or timestamp modes when creating and switching to a new feature branch.

Does this branching automation work with custom environment overrides?

Yes, this branching automation supports environment overrides for custom branch names. It applies a configurable naming scheme that integrates with your software development workflows, allowing custom environment variables to dictate branch naming.

When do I need an automated tool for feature branch creation?

You need an automated tool for feature branch creation when managing disciplined branching for features and experiments across multiple teams. It solves the problem of manually enforcing naming conventions and sequential or timestamp numbering schemes in Git workflows.

Are there limitations to using environment overrides for custom branch names?

The main limitation is that environment overrides for custom branch names must align with the enforced configurable naming scheme. While it supports custom names via environment variables, the sequential or timestamp numbering modes are handled strictly via Git tooling.