speckit-git-feature

To automatically create numbered Git feature branches for spec-kit, the workflow parses your repository's configuration files to select a numbering strategy, then delegates to platform-specific scripts to generate and check out the branch with a sequentially or timestamp-derived number.

Branch numbering works by reading your preferred strategy from git-config.yml or init-options.json. It assigns sequential numbers by default, or timestamp-based numbers if configured, ensuring consistent branch naming across specifications.

Yes, you can override the generated branch name by setting the GIT_BRANCH_NAME environment variable. This bypasses the default prefix and suffix generation, preserving the exact branch name you provide.

Automating branch creation requires a spec-kit repository structure with a .specify directory. The script prefers reading settings from .specify/extensions/git/git-config.yml, then falls back to .specify/init-options.json to determine the numbering strategy.

No, the branch creation script does not generate specification files. It exclusively creates and checks out the Git feature branch, leaving the spec directory and file creation to the core spec-kit workflow.

You need Git installed and available in your environment, a spec-kit repository with a .specify directory, and your numbering strategy configured in git-config.yml or init-options.json to run the automation successfully.