speckit-git-feature

Create and switch to numbered git feature branches with JSON output.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT --skill speckit-git-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT/tree/main/.agent/skills/speckit-git-feature
Command: npx skills add https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT --skill speckit-git-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and naming of git feature branches so teams have consistent, predictable branch names and numeric or timestamp prefixes without manual bookkeeping.

Core Features & Use Cases

  • Consistent Branch Naming: Generates concise short names and either sequential numeric prefixes or timestamp prefixes based on repository configuration.
  • Cross-Platform Execution: Invokes platform-specific scripts (Bash or PowerShell) and always requests JSON output containing BRANCH_NAME and FEATURE_NUM for downstream automation.
  • Graceful Degradation & Overrides: Detects absence of Git or non-repo contexts, emits warnings while still returning branch metadata, and supports explicit overrides via the GIT_BRANCH_NAME environment variable.
  • Use Case: Use when opening a new specification-driven feature so the branch is created with the correct numeric sequence and can be referenced by automated workflows.

Quick Start

Create a new sequential feature branch for "add user authentication" using the speckit-git-feature skill.

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 sequential numbering?

Automated git feature branch creation generates consistent, predictable branch names with sequential numeric or timestamp prefixes without manual bookkeeping. It invokes platform-specific scripts to create and switch branches, emitting JSON metadata containing BRANCH_NAME and FEATURE_NUM for downstream automation workflows.

Do I need the spec-kit .specify structure to create numbered feature branches?

The spec-kit .specify structure is required to create numbered feature branches. This branch creation process applies to repositories using the spec-kit structure and requires Git availability alongside the spec-kit git extension scripts to generate sequential or timestamped branch names correctly.

Can I override the generated git feature branch name manually?

You can override the generated git feature branch name manually using the GIT_BRANCH_NAME environment variable. This explicit override allows custom branch naming while still returning the standard JSON output containing BRANCH_NAME and FEATURE_NUM for workflow automation tracking.

Does this git feature branch workflow support both Unix and Windows environments?

This git feature branch workflow supports both Unix and Windows environments by invoking platform-specific scripts. It automatically utilizes Bash scripts on Unix systems and PowerShell scripts on Windows to ensure cross-platform execution when generating numbered feature branches.

What happens if Git is not available when generating a feature branch?

When Git is not available or the context is a non-repository, the feature branch generation process degrades gracefully. It detects the absence, emits warnings, and still returns branch metadata in JSON format so downstream automation workflows do not break unexpectedly.

Why use sequential numeric prefixes for git feature branches in specification workflows?

Sequential numeric prefixes for git feature branches ensure consistent, predictable naming across specification workflows. Teams can reference branches by their correct numeric sequence, enabling automated workflows to track and process specification-driven features reliably without manual bookkeeping errors.