Skip to content
TrustedSkillsbeta
Back to all skills

Release Bump

Checked
mikeyobrien·vlatest·devops·MIT

Automatically increments version numbers in files & manifests for seamless releases – streamlining your DevOps workflows and reducing manual errors.

Repository

Install on your platform

This skill no longer installs under the name release-bump. SKILL.md is marked internal, so the skills CLI hides it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-16. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

mikeyobrien

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mikeyobrien/ralph-orchestrator at edc2b3268c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
edc2b3268c
Manifest
.claude/skills/release-bump/SKILL.md
Scanned
1 file, 62 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The release-bump skill automates incrementing version numbers in project files. It can update semantic versions (e.g., 1.2.3 to 1.2.4) within a specified file or across an entire repository, and supports various formats like package.json, pom.xml, and more. This helps streamline software release processes by ensuring accurate versioning.

When to use it

  • Automated releases: Increment the version number when deploying a new build to a staging or production environment.
  • Dependency updates: Automatically bump versions after merging pull requests that include dependency changes.
  • Internal tooling: Update version numbers in internal tools and libraries as part of their development cycle.
  • Release branches: Increment the version number when creating a release branch from main.

Key capabilities

  • Supports various file formats (package.json, pom.xml, etc.)
  • Increments semantic versions (major, minor, patch)
  • Can operate on single files or entire repositories
  • Automates versioning tasks within software development workflows.

Example prompts

  • "Bump the version in package.json from 1.0.0 to 1.0.1."
  • "Increment the patch version in all pom.xml files in this repository."
  • “Update the version number in my project’s main configuration file.”

Tips & gotchas

  • Ensure you have appropriate permissions to modify the target files or repositories.
  • Review any changes made by the skill before committing them to your codebase, especially when operating on entire repositories.