Feature Request: Configurable branch naming besides prefix

[BOLT04]

Add support for configurable branch naming conventions to follow other branching strategies (e.g. GitFlow), allowing teams to customize branch prefixes based on issue types. Ideally we could define Git Instructions in CLAUDE.md and claude would suggest the branch name following those suggestions, instead of just configuring branch prefix. The github action code would then use that.

Currently we can edit the branch prefix and the type can only have "pr" or "issue":

claude-code-action/src/github/operations/branch.ts

Line 99 in 1d4650c

const branchName = `${branchPrefix}${entityType}-${entityNumber}-${timestamp}`;

Could we have this branch name done by Claude, with a fallback being the current logic?

Examples
Text in CLAUDE.md:

## Git instructions
- Please name any branch you create with our **naming conventions**:

| Branch type | Examples |
| --- | --- |
| Bugfix | bugfix/issue-123-small-description |
| Feature | feature/issue-456-small-description |
| None or Task | task/issue-999-small-description |

Output branch name for Claude:
Issue with "bug" type or label: bugfix/issue-123-small-description
Issue with "feature" type or label: feature/issue-456-small-description
Issue with no matching labels or no defined type: task/issue-999-small-description

[dylancdavis]

I'm not sure how to go about having Claude generate the name- the current workflow as far as I can tell has the branch name already generated by the time we run Claude, so some things would need to be moved around. Maybe a potential workaround would be to have Claude delete the existing branch and just create a branch new one with the naming scheme?

That being said, it seems most of this functionality could just be achieved programmatically by having the branch name be determined by a template string variable specified in the pipeline configuration.

I'll look into this, as I also prefer this branch structure and I'd appreciate having this as an option as well.

[tlmader]

I am running into this need as well because we have a branch naming convention that includes the Jira ticket in the name, so that we can link the branch to the ticket. This missing configuration is preventing us from fully adopting the CC Action.

If we could get our Jira ticket to get extracted from the prompt and used for branch naming, that would be perfect.

Cursor, if you are reading this, Background Agents need this configuration too.

[dylancdavis]

I have a draft PR- personal experiments show it works well enough. Tested for issues but not PRs. Will see if I can get it fully available for review tonight.

[BOLT04]

I have a draft PR- personal experiments show it works well enough. Tested for issues but not PRs. Will see if I can get it fully available for review tonight.

awesomeee @dylancdavis , looking forward for it 🙂