speckit-git-feature

Creates and switches to a new git feature branch for a specification.

1.0k|514|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada --skill speckit-git-feature-unipds-engenharia-de-ia-aplicada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada/tree/main/lives/2026-05-27/001-pos-live/.claude/skills/speckit-git-feature
Command: npx skills add https://github.com/unipds-engenharia-de-ia-aplicada/engenharia-de-software-com-ia-aplicada --skill speckit-git-feature-unipds-engenharia-de-ia-aplicada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual friction of creating consistent git feature branches for new specifications, helping teams start work with the right branch name and numbering scheme every time.

Core Features & Use Cases

  • Branch Creation: Creates and switches to a new feature branch using either sequential or timestamp-based numbering.
  • Configuration Awareness: Reads spec-kit branch-numbering settings and honors explicit branch name overrides when provided.
  • Graceful Fallbacks: Detects whether Git and the expected repository structure are available, then skips safely if prerequisites are missing.
  • Use Case: A developer starts a new feature or spec task and needs an automatically named branch that matches the project’s conventions.

Quick Start

Use the speckit-git-feature skill to create and switch to a new git feature branch for your specification using the project’s naming 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 create a git feature branch with sequential or timestamp-based naming?

To create a git feature branch with consistent naming, the skill reads spec-kit branch-numbering configuration and automatically creates and switches to a new branch using either sequential or timestamp-based numbering schemes. It honors explicit branch name overrides when provided.

What is the best way to automate feature branch creation for spec-kit repositories?

Automating feature branch creation for spec-kit repositories involves using a skill that verifies Git availability, respects the project's branch-numbering settings, and generates a new branch matching the team's conventions without manual friction.

Do I need Git installed to create feature branches for new specifications?

Yes, you need Git installed to create feature branches. The skill verifies Git availability and checks for the expected repository structure before creating the branch, falling back gracefully and skipping safely if these prerequisites are missing.

Can I override the automatic branch name when starting a new spec task?

Yes, you can override the automatic branch name. While the skill applies sequential or timestamp-based numbering from spec-kit configuration by default, it explicitly honors branch name overrides provided by the developer for new specifications.

What happens if I run feature branch creation outside a git repository?

If you run feature branch creation outside a git repository, the skill detects the missing repository structure and Git availability, then skips the operation gracefully without throwing errors, ensuring a safe fallback when prerequisites are not met.