speckit-git-feature

Create and switch to numbered git feature branches from a specification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and switching to a new git feature branch based on a specification, ensuring consistent naming and reducing manual errors during feature work.

Core Features & Use Cases

  • Deterministic branch naming with sequential or timestamp prefixes based on configuration or environment overrides.
  • Automatic branch creation and checkout, with optional GIT_BRANCH_NAME override.
  • Compatibility with the spec-kit workflow and .specify/ directory for branch specification.
  • Graceful handling when Git is unavailable or not in a repository; outputs BRANCH_NAME and FEATURE_NUM for downstream automation.

Quick Start

Describe a feature or task and let the tool generate and switch to the appropriate feature branch according to the configured numbering rules.

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 deterministic naming?

To automate git feature branch creation, this tool reads a feature specification and branch_numbering configuration to generate a deterministic branch name. It creates and switches to the branch automatically, outputting BRANCH_NAME and FEATURE_NUM variables for downstream automation workflows.

What is deterministic feature branch numbering in git workflows?

Deterministic feature branch numbering is a standardized git workflow process that assigns sequential or timestamp-based prefixes to feature branches. This ensures consistent naming, reduces manual errors, and provides traceable FEATURE_NUM outputs for downstream automation tracking.

Can I override the generated git feature branch name with an environment variable?

Yes, the generated git feature branch name can be overridden using the GIT_BRANCH_NAME environment variable. When configured, this variable takes priority over the standard sequential or timestamp numbering generated from the branch_numbering configuration.

Does this automated branch creation tool work without an active git repository?

The automated branch creation tool validates git availability and handles environments without an active git repository gracefully. If git is missing or the directory is not a repository, it skips branch creation while still outputting BRANCH_NAME and FEATURE_NUM for automation continuity.

How do I configure sequential versus timestamp numbering for feature branches?

Configuring sequential versus timestamp numbering for feature branches is managed through the branch_numbering configuration file. The tool reads this configuration to determine the prefix format, ensuring standardized naming across the software development workflow.

What is the best way to standardize feature branch naming across a development team?

The best way to standardize feature branch naming is to use a specification-driven automation tool that applies deterministic sequential or timestamp prefixes. This enforces consistent naming, eliminates manual errors, and integrates with spec-kit workflows via the .specify/ directory.