speckit-git-feature

To create a Git feature branch automatically, the skill reads your repository's configured numbering strategy and switches to a new branch without manual naming. It applies sequential or timestamp-based prefixes to generate consistent branch names for spec-driven development.

Yes, you can specify an exact Git branch name by providing the GIT_BRANCH_NAME environment variable. When this variable is set, the skill preserves your exact branch name and bypasses the automatic short-name generation and numbering configuration.

Yes, feature branch creation works in both Bash and PowerShell environments. The skill applies environment-variable overrides across both shell types, allowing you to generate branches consistently regardless of your operating system.

If Git is not available, the skill degrades safely without failing. It verifies Git availability before attempting branch creation, ensuring your workflow falls back gracefully rather than throwing errors when the version control system is missing.

The best way to standardize feature branch naming is to use a centralized skill that reads branch-numbering configuration from the repository. This enforces sequential or timestamp-based prefixes and short-name generation, removing manual naming inconsistencies across developers.

You need branch-numbering configuration present in your spec-kit project so the skill can read it. Once configured, it automatically applies your chosen sequential or timestamp-based strategy, requiring no manual branch numbering input during creation.