create-release-branch
Skill107 starsChanged 9 months agoMITView on GitHub
Create a release branch for a given version. Use when you want to start a release, cut a release branch, or bump the version for a new release. Creates release/<version> from develop, updates version.rb, and commits the version bump.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nexus-a1/claude-skillstheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nexus-a1/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- commitSkill
- create-pull-requestSkill
- create-release-notesSkill
- handle-pr-reviewSkill
- qlty-checkSkill
- record-code-review-feedbackSkill
- record-spec-feedbackSkill
- recreate-test-dbSkill
- redmine-playwright-loginSkill
- regression-checkSkill
- rubocopSkill
- speckit-agent-context-updateSkill
- speckit-analyzeSkill
- speckit-branch-convention-configureSkill
- speckit-branch-convention-renameSkill
- speckit-branch-convention-validateSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-review-codeSkill
- speckit-review-commentsSkill
- speckit-review-errorsSkill
- speckit-review-runSkill
- speckit-review-simplifySkill
- speckit-review-testsSkill
- speckit-review-typesSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- speckit-token-budget-compactSkill
- speckit-token-budget-conciseSkill
- speckit-token-budget-scopeSkill
- speckit-token-budget-usageSkill
- speckit-wiki-ingestSkill
- speckit-wiki-initSkill
- speckit-wiki-lintSkill
- speckit-wiki-querySkill
- speckit-wiki-statusSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Create a release/<version> branch from develop, bump the version in version.rb, and commit the change.
- Very specific: line 25
Read version.rb and note the current VERSION value.
- Very specific: line 29
Run git branch -a | grep release to check whether a release/<version> branch already exists.
- Distinctive: line 30
If it already exists, stop and report it to the user instead of recreating it.
- Very specific: line 34
Create the branch from develop:
- Distinctive: line 59
Do not push. Report the branch name and commit to the user.
- Distinctive: line 63
Follow the project rule: never push without explicit user instruction.
- Distinctive: line 64
Commit messages must be plain English with no reference to Claude Code.
- Very specific: line 66
After this skill, the create-pull-request skill can open the release PR against main.
- Very specific: line 70
If version.rb is missing or the VERSION constant cannot be found, stop and report it.
- Distinctive: line 71
If the working tree has the release branch already checked out or the branch exists, do not overwrite — report the current state.
- Distinctive: line 72
If the requested version is not valid semver, ask the user to confirm before proceeding.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create Release Branch
Create a release/<version> branch from develop, bump the version in version.rb, and commit the change.
User Input
$ARGUMENTSThe user input should contain the target release version (e.g. 3.3.0). If no version is provided, ask the user which version to release before proceeding.
Procedure
Step 1: Confirm the Current Version
Read version.rb and note the current VERSION value. Confirm the requested version is different and follows semantic versioning (MAJOR.MINOR.PATCH).
Step 2: Check for an Existing Release Branch
Run git branch -a | grep release to check whether a release/<version> branch already exists.
- If it already exists, stop and report it to the user instead of recreating it.
Step 3: Create the Release Branch
Create the branch from develop:
git checkout -b release/<version> developStep 4: Bump the Version
Edit version.rb and update the VERSION constant to the new <version>.
module RedmineAiHelper
VERSION = "<version>"
endStep 5: Commit the Version Bump
Stage only version.rb (do not include unrelated changes such as .claude/settings.json) and commit:
git add version.rb
git commit -m "Bump version to <version>"Do not push. Report the branch name and commit to the user.
Notes
- Follow the project rule: never push without explicit user instruction.
- Commit messages must be plain English with no reference to Claude Code.
- Stage only the version bump; leave any other working-tree changes untouched.
- After this skill, the
create-pull-requestskill can open the release PR againstmain.
Error Handling
- If
version.rbis missing or theVERSIONconstant cannot be found, stop and report it. - If the working tree has the release branch already checked out or the branch exists, do not overwrite — report the current state.
- If the requested version is not valid semver, ask the user to confirm before proceeding.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

