speckit-git-feature

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

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill speckit-git-feature-inspedralbes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW/tree/main/prj-entrades-nou/.cursor/skills/speckit-git-feature
Command: npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill speckit-git-feature-inspedralbes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating feature branches manually can lead to inconsistent naming and wasted time. This Skill automates the creation and switching to a new git feature branch based on a given specification, ensuring consistent branch context for each feature.

Core Features & Use Cases

  • Automated feature-branch creation: Generates a branch name from the specification and switches to it.
  • Flexible numbering: Supports sequential or timestamp-based branch numbers, with optional environment overrides.
  • Graceful degradation: If Git is unavailable, it reports the intended branch name and feature number without failing the workflow.

Quick Start

Provide a specification and run the speckit-git-feature workflow to create and switch to the new 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 automatically create and name Git feature branches?

Automatically create and name Git feature branches by providing a specification to generate a branch name and switch to it. This enforces configuration-driven branch numbering, ensuring consistent naming context for each feature.

Can I use sequential or timestamp-based numbering for feature branch naming?

Yes, feature branch naming supports flexible numbering using either sequential or timestamp-based branch numbers. You can also apply optional environment overrides to customize the branch numbering strategy.

What happens if Git is unavailable when generating a feature branch?

If Git is unavailable, the workflow gracefully degrades without failing. It reports the intended branch name and feature number, always returning the BRANCH_NAME and FEATURE_NUM variables for downstream use.

What is the best way to enforce consistent feature branch naming across a team?

The best way to enforce consistent feature branch naming is to use an automated workflow that generates branch names from a given specification. This applies configuration-driven numbering and eliminates manual naming errors.

Do I need Git installed to generate a feature branch name and number?

You do not need Git installed to generate a feature branch name and number. The workflow checks for Git presence and gracefully degrades, returning the BRANCH_NAME and FEATURE_NUM without failing if Git is unavailable.