How can I use my own branch patterns instead of 001-*?

[Tarasovych]

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

[ernestjumbe]

You might need to edit the check-prerequisites.sh or 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]

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] here

[ernestjumbe]

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]

You can use your own branch naming pattern by updating the following files:

• create-new-feature.sh: Mainly the generate_branch_name function
• common.sh: get_current_branch function
• You many also have to update the agent file of specify to include details of your naming pattern

[chrisisagile]

I cheat... I have it create the branch right up until my first commit/push, and before I do that I tell it to rename my branch following my branch naming rules. I tried changing the code but found myself fighting way too much with it since my branch naming approach does NOT start with an id indexer.