[Feature]: Configurable branch naming convention

[aaronkerckhoff]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

Not sure

Problem or use case

Currently all branches created by T3-Code default to the naming scheme t3code/{some-slug}. There isn't a way to configure branch naming to fit own repo standards or conventions.

Proposed solution

It would be nice to be able to change that to a few presents. I, for one, like my feature-branches to be named "feat/..." or "fix/...", etc. A few templates could be

• t3code/{slug} (current)
• {type}/{slug}
• {slug} (without any prefix)
• possibly {type}/{threadId}-{slug}

I'd be happy to implement this feature, if approved.

Why this matters

This would allow developers to comply with standards embraced by some repositories over years, as well as allowing personal preferences to be respected.

Smallest useful scope

A new setting that allows to switch between 2-4 different branch-naming templates.

Alternatives considered

I currently just write a few lines in all my AGENTS.md to create a new branch, commit and PR manually and paste the link in chat. However, that makes the nice feature to have a separate section for Source Control in T3-Code obsolete.

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[juliusmarminge]

#7063 requests the same configurable branch naming, including no prefix, feat/fix prefixes, user namespaces and repository-derived names. Please retain its worktree-directory naming example and the maintainer suggestion to allow custom generation instructions when designing this setting.

[jcampuza]

+1 on this, though I think most harnesses keep the configuration pretty simple of just specifying the prefix. At the very least having that would be great and solve I think 99% of cases for this.