agentleFS
haruharu/redmine_ai_helper/.claude/skills/create-release-branch/SKILL.md

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

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
  1. Very specific:

    Create a release/<version> branch from develop, bump the version in version.rb, and commit the change.

    line 11
  2. Very specific:

    Read version.rb and note the current VERSION value.

    line 25
  3. Very specific:

    Run git branch -a | grep release to check whether a release/<version> branch already exists.

    line 29
  4. Distinctive:

    If it already exists, stop and report it to the user instead of recreating it.

    line 30
  5. Very specific:

    Create the branch from develop:

    line 34
  6. Distinctive:

    Do not push. Report the branch name and commit to the user.

    line 59
  7. Distinctive:

    Follow the project rule: never push without explicit user instruction.

    line 63
  8. Distinctive:

    Commit messages must be plain English with no reference to Claude Code.

    line 64
  9. Very specific:

    After this skill, the create-pull-request skill can open the release PR against main.

    line 66
  10. Very specific:

    If version.rb is missing or the VERSION constant cannot be found, stop and report it.

    line 70
  11. Distinctive:

    If the working tree has the release branch already checked out or the branch exists, do not overwrite — report the current state.

    line 71
  12. Distinctive:

    If the requested version is not valid semver, ask the user to confirm before proceeding.

    line 72

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create Release Branch

Create a release/<version> branch from develop, bump the version in version.rb, and commit the change.

User Input

$ARGUMENTS

The 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> develop

Step 4: Bump the Version

Edit version.rb and update the VERSION constant to the new <version>.

module RedmineAiHelper
  VERSION = "<version>"
end

Step 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-request skill can open the release PR against main.

Error Handling

  • If version.rb is missing or the VERSION constant 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.