speckit-git-feature

Generate and switch to numbered Git feature branches in spec-kit projects.

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-git-feature-apothecaryman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-git-feature-apothecaryman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of creating feature branches in Git, automatically applying sequential or timestamp-based numbering to ensure a consistent naming convention.

Core Features & Use Cases

  • Sequential Branch Naming: Automatically generates branch names based on a sequential number prefix.
  • Timestamp Branch Naming: Allows the creation of branches with a timestamp prefix, ideal for time-stamped releases.
  • Spec-Kit Compatibility: Designed to work with projects structured using the spec-kit project system.

Quick Start

Run the 'create feature branch' command to generate a new feature branch for your project.

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 Git feature branch with an automated sequential number prefix?

To create a Git feature branch with an automated sequential number, you can use this Skill to generate and switch to a new branch. It automatically applies a sequential numbering convention to ensure consistent branch naming within your project.

Can I use a timestamp instead of sequential numbers for Git branch naming?

Yes, you can use a timestamp instead of sequential numbers for Git branch naming. This Skill supports both sequential and timestamp-based numbering, allowing you to choose timestamp prefixes for time-stamped releases or chronological tracking.

Does this feature branch generator work without a spec-kit project structure?

No, this feature branch generator requires a spec-kit project structure to function correctly. It specifically looks for a .specify/ directory within your repository to streamline the branching process for spec-kit structured projects.

What is the best way to maintain consistent naming conventions for feature branches?

The best way to maintain consistent naming conventions for feature branches is to automate the process. This Skill enforces a standardized naming format by automatically generating branch names with sequential or timestamp-based prefixes.

Why do I need a .specify/ directory for feature branch creation?

You need a .specify/ directory because this Skill is designed to integrate with the spec-kit project system. This directory confirms the project structure and enables the automated feature branch generation process to run correctly.