Safely updates the version number in BreakEscape gem projects while preventing CI failures from lockfile drift.
Install
mkdir -p .claude/skills/bump-version-cliffe && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18130" && unzip -o skill.zip -d .claude/skills/bump-version-cliffe && rm skill.zipInstalls to .claude/skills/bump-version-cliffe
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Bumps the BreakEscape gem version and keeps Gemfile.lock in sync. Trigger when the user asks to "bump the version", "release a new version", "increment the version", or "update the version number".Key capabilities
- →Determine the new version number for the gem
- →Update the VERSION constant in lib/break_escape/version.rb
- →Manually update the PATH section of Gemfile.lock
- →Report the old and new versions to the user
- →Suggest a commit message for the version bump
How it works
The skill updates the gem version by modifying lib/break_escape/version.rb and manually syncing Gemfile.lock to prevent CI failures, then reports the changes.
Inputs & outputs
When to use bump-version
- →Incrementing a gem version
- →Preparing a project for a new release
- →Fixing gem version sync issues in CI
About this skill
Break Escape bump-version skill
Update the version in the one canonical place and regenerate the lockfile so CI doesn't fail.
Step 1 — determine the new version
If the user specified a version, use it. Otherwise read the current version and increment the patch number (third digit), e.g. 1.0.4 → 1.0.5:
cat lib/break_escape/version.rb
Step 2 — update the version file
Edit lib/break_escape/version.rb — change only the VERSION constant string. Do not touch ASSETS_VERSION.
Step 3 — update Gemfile.lock manually
The PATH section of Gemfile.lock embeds the gem version. After changing VERSION, it will be out of sync and CI will fail with "The gemspecs for path gems changed" in deployment mode.
Update it directly — change only the version on the break_escape (X.Y.Z) line in the PATH block:
PATH
remote: .
specs:
break_escape (1.0.5) ← update this line
Do not run bundle install — the global ~/.bundle/config has a mirror pointing to a local Hacktivity cache path that doesn't exist, which causes bundle install to fail in this project.
Step 4 — confirm and report
Tell the user:
- The old version and the new version
- That
Gemfile.lockwas updated (show the new PATH block) - That both files should be committed together
Suggest a commit message like: chore: bump version to X.Y.Z
When not to use it
- →When the user wants to use standard bundler commands for version bumping
- →When the project's global ~/.bundle/config does not cause bundle install to fail
- →When only ASSETS_VERSION needs to be changed
Limitations
- →Only bumps the BreakEscape gem version
- →Does not use bundle install due to project-specific configuration issues
- →Only changes the VERSION constant, not ASSETS_VERSION
How it compares
This skill manually updates Gemfile.lock to avoid issues with a specific bundler configuration, unlike typical version bumping processes that rely on automated bundler commands.
Compared to similar skills
bump-version side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| bump-version (this skill) | 0 | 1mo | Review | Beginner |
| upgrade-dependencies | 0 | 3mo | Review | Intermediate |
| gcp-cloud-run | 5 | 4mo | Review | Intermediate |
| flow-nexus-platform | 6 | 4mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
upgrade-dependencies
codenamev
Upgrade all Ruby gem dependencies to their latest versions with release note review and codebase alignment checks. Use this skill whenever the user asks to update, upgrade, or bump dependencies, gems, or packages — even casually like 'update my gems' or 'are my deps up to date?'
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.