speckit-git-feature

Create a Git feature branch from a specification with configured naming conventions.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill speckit-git-feature-majedsiefalnasr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/majedsiefalnasr/bunyan-app-cursor/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill speckit-git-feature-majedsiefalnasr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and naming feature branches for specs can be error-prone and time-consuming; this skill streamlines the process by generating a correctly formatted branch name and switching to it, so developers can start work immediately.

Core Features & Use Cases

  • Generates a new git feature branch from a specification, ensuring branch names follow configured conventions (sequential or timestamp-based).
  • Supports overriding the branch name via GIT_BRANCH_NAME to bypass automatic prefixing or numbering.
  • Integrates with the speckit.specify workflow to isolate branch creation from spec generation.

Quick Start

Provide a specification and run the speckit workflow to generate 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 automatically create a git feature branch from a specification?▼

To automatically create a git feature branch from a specification, provide the spec to the speckit workflow. The process generates a correctly formatted branch name and switches to it, ensuring naming follows configured conventions.

Can I override the automatic feature branch naming convention in git?▼

Yes, you can override the automatic feature branch naming convention by providing a GIT_BRANCH_NAME variable. This bypasses the configured sequential or timestamp-based prefixing and numbering modes.

Does the speckit workflow support both sequential and timestamp-based branch numbering?▼

The speckit workflow supports both sequential and timestamp-based branch numbering modes. It reads the branch_numbering configuration from the .specify file to determine which numbering format to apply.

What is the best way to isolate feature branch creation from spec generation?▼

The best way to isolate feature branch creation from spec generation is using the speckit workflow integration. It handles branch generation and switching separately, outputting BRANCH_NAME and FEATURE_NUM for tracking.

Why does my feature branch creation fail when the .specify configuration is missing?▼

Feature branch creation may fail without the .specify configuration because the skill reads branch_numbering settings from this file to determine sequential or timestamp-based naming conventions. Ensure this file exists before running the workflow.

How do I start working immediately after generating a new feature branch?▼

To start working immediately after generating a new feature branch, run the speckit workflow with your specification. It automatically switches to the newly created branch so developers can begin coding without manual checkout.