speckit-git-feature

Create and switch git feature branches using project-defined naming conventions.

Updated May 31, 2026
One-click install
npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-git-feature-piklar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/Piklar/Rizza-60/tree/main/.agents/skills/speckit-git-feature
Command: npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-git-feature-piklar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates manual branch naming inconsistencies and ensures that every feature branch follows a project-specific, sequential or timestamped naming convention.

Core Features & Use Cases

  • Automated Branching: Automatically generates branch names based on project configuration and feature descriptions.
  • Flexible Numbering: Supports both sequential numbering and timestamp-based prefixes to maintain a clean git history.
  • Use Case: When starting a new task, use this skill to create a branch named 005-add-user-auth, ensuring it aligns with your team's existing branch numbering strategy without manual effort.

Quick Start

Ask the system to create a new feature branch for the user authentication module 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 naming conventions?▼

Automating git feature branch creation requires applying project-defined naming conventions to generate sequential or timestamped branch prefixes. This eliminates manual naming inconsistencies by automatically switching to branches like 005-add-user-auth based on your project configuration.

What's the best way to standardize feature branch naming across a development team?▼

Standardizing feature branch naming is achieved by enforcing project-specific sequential or timestamped prefixes during branch creation. This ensures every team member generates consistent branch identification without manual effort, maintaining a clean git history.

Do I need a specific project structure to automate git branching workflows?▼

Automating git branching workflows requires a valid git repository and adherence to the spec-kit project structure. This specific configuration layout is necessary for the skill to successfully look up and apply your project's defined numbering conventions.

Can I use timestamped prefixes instead of sequential numbering for git branches?▼

Using timestamped prefixes instead of sequential numbering for git branches is fully supported. You can configure the branching workflow to apply either sequential numbering or timestamp-based prefixes to maintain your preferred version control history.

How does automated branch generation handle existing sequential branch numbers?▼

Automated branch generation handles existing sequential numbers by reading project configuration to determine the next appropriate prefix. It applies sequential numbering or timestamp-based prefixes to ensure new branches align with your team's existing branch numbering strategy.

When should I not use automated branch creation in my version control workflow?▼

Automated branch creation should not be used when your repository lacks the required spec-kit project structure configuration. Without this specific setup, the skill cannot look up the necessary project-defined naming conventions to generate consistent branch names.