Repository navigation
How can I use my own branch patterns instead of 001-*? #1518
Description
I have this inside constitution:
**Branching**:
- Three branch formats only: `feature/`, `bugfix/`, `chore/`
- All branches must have one of these three prefixes
- Format: `feature/module-description`, `bugfix/issue-number-title`, `chore/task-description`
- Main branch always deployable
Looks like spec-kit does not respect this
Activity
ernestjumbe commentedon Jan 24, 2026
You might need to edit the
check-prerequisites.shor the corresponding file depending on your operating system. This is where the branching is validated. Don't look at this project as a one size fits all solution. Fork and tinker according to your needs.Tarasovych commentedon Jan 27, 2026
Thanks, found it in
create-new-feature.sh. Do you know if spec-kit will auto pick new arguments, say, if I add custom argument like [feature/chore/bugfix] hereernestjumbe commentedon Jan 27, 2026
Every time this script is referenced, it will apply the strategy. you might need to also look into each of the shell script files to make sure the rules you have set are consistent during the branch checks.
samhoooo commentedon Feb 23, 2026
You can use your own branch naming pattern by updating the following files:
create-new-feature.sh: Mainly thegenerate_branch_namefunctioncommon.sh:get_current_branchfunctionspecifyto include details of your naming pattern