Problem Statement
CONTRIBUTING.md asks contributors to use branch names like feature/add_new_plot or bug/fix_units, and the /create-pr and /update-pr slash commands derive a pull request's [FEATURE] or [BUG] title prefix from that branch name prefix. This requirement has two problems. First, it often isn't clear whether a branch will end up delivering a feature implementation or a bug fix until development is well underway, so the branch name locks in a classification before it can be made accurately. Second, the rule says nothing about work that includes both a bug fix and a new feature, which happens in practice: issue #267 carries both the bug and feature labels.
Location(s): CONTRIBUTING.md, .claude/commands/create-pr.md, .claude/commands/update-pr.md, .claude/commands/open-issue.md
Proposed Solution
- Remove the prefix requirement from
CONTRIBUTING.md, keeping the advice to use descriptive branch names.
- Update
.claude/commands/create-pr.md and .claude/commands/update-pr.md so the [FEATURE] and [BUG] title prefixes are chosen from the pull request's labels rather than the branch name, matching how issue title prefixes already work. This includes deciding how to prefix a title when both labels apply. Also touch up the clause in .claude/commands/open-issue.md that contrasts label-driven issue prefixes with branch-driven pull request prefixes, since that contrast goes away.
- Rename any existing branches that still carry a
feature/ or bug/ prefix.
Problem Statement
CONTRIBUTING.mdasks contributors to use branch names likefeature/add_new_plotorbug/fix_units, and the/create-prand/update-prslash commands derive a pull request's[FEATURE]or[BUG]title prefix from that branch name prefix. This requirement has two problems. First, it often isn't clear whether a branch will end up delivering a feature implementation or a bug fix until development is well underway, so the branch name locks in a classification before it can be made accurately. Second, the rule says nothing about work that includes both a bug fix and a new feature, which happens in practice: issue #267 carries both thebugandfeaturelabels.Location(s):
CONTRIBUTING.md,.claude/commands/create-pr.md,.claude/commands/update-pr.md,.claude/commands/open-issue.mdProposed Solution
CONTRIBUTING.md, keeping the advice to use descriptive branch names..claude/commands/create-pr.mdand.claude/commands/update-pr.mdso the[FEATURE]and[BUG]title prefixes are chosen from the pull request's labels rather than the branch name, matching how issue title prefixes already work. This includes deciding how to prefix a title when both labels apply. Also touch up the clause in.claude/commands/open-issue.mdthat contrasts label-driven issue prefixes with branch-driven pull request prefixes, since that contrast goes away.feature/orbug/prefix.