speckit-git-feature

Creates and checks out a Git feature branch with sequential or timestamped numbering.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a new Git feature branch with consistent naming and automatic sequencing or timestamp-based identifiers to align with specification-driven workflows.

Core Features & Use Cases

  • Consistent feature branch naming that reflects the specification
  • Supports sequential numbering or timestamp-based branch names
  • Enables overriding the branch name via the GIT_BRANCH_NAME environment variable
  • Graceful handling when Git is not available and alignment with the specify workflow

Quick Start

Create and switch to a new feature branch using the naming convention derived from the specification.

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 new Git feature branch with consistent naming?

To create a new Git feature branch with consistent naming, this Skill automates the checkout process using sequential or timestamp-based identifiers derived from your specification. It ensures branch names align with spec-driven development workflows automatically.

What is spec-driven development branch naming?

Spec-driven development branch naming is the process of creating Git branches that reflect the related specification. This mechanism derives the next branch number from config files or defaults to sequential numbering to maintain consistency across feature development.

Can I override the Git branch name during feature development?

Yes, you can override the Git branch name by setting the GIT_BRANCH_NAME environment variable. The Skill respects this override and will use your specified name instead of generating a sequential or timestamp-based identifier.

How do I generate timestamp-based Git feature branches?

You can generate timestamp-based Git feature branches by using this automation Skill configured for timestamp-based identifiers. It automatically creates and switches to a new branch using the naming convention derived from your specification.

Does this branch creation workflow work if Git is not available?

No, if Git is not available, this Skill handles the situation gracefully rather than failing. However, since it enforces branch creation by automating Git checkout commands, a Git repository is required for actual branch creation.

What's the best way to automate feature branch creation in a specification workflow?

The best way to automate feature branch creation in a specification workflow is to use a Skill that derives branch numbers from config files and aligns branch names with the related spec. This ensures consistent naming and automatic sequencing for spec-driven development.