New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Bump Version Dev

by lycorp-jp in lycorp-jp/sim-use

Build a release-shaped sim-use binary and install it locally for testing.

Apache-2.0Auto-check passedMobile

Install Bump Version Dev

skills CLI
$ npx skills add lycorp-jp/sim-use --skill bump-version-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install lycorp-jp/sim-use bump-version-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/lycorp-jp/sim-use.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bump-version-dev .claude/skills/bump-version-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bump-version-dev
GitHub stars
1.4k
Token cost
~1k tokens
SKILL.md length
469 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build a release-shaped sim-use binary and install it locally for testing.

  • Works in 5 steps: Pre-flight → Determine the next version → Confirm with the user → …
  • The user runs /bump-version-dev
  • SKILL.md covers Restore flow, Step 1: Pre-flight, Step 2: Determine the next… and Step 3: Confirm with the user, plus 3 more sections
  • Calls git

What it does

Bump Version Dev is an agent skill from lycorp-jp/sim-use. Build a release-shaped sim-use binary and install it locally for testing. Use when the user runs /bump-version-dev or asks to "build a dev release", "test the release build locally", "install a release build for testing", or "prepare a release candidate without publishing". Builds APK + CLI, stages, ad-hoc signs, and repoints the PATH binary. Does NOT commit, tag, push, create releases, or update homebrew. After local validation, run /release to ship for real.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering App store release. It works with Homebrew, Android and Git. The repository describes itself as: Give your AI agent eyes and hands on iOS Simulator and Android emulator/devices. The licence is Apache-2.0.

When your agent uses it

  • The user runs /bump-version-dev
  • Asks to build a dev release
  • Test the release build locally
  • Install a release build for testing

Example prompts

  • “build a dev release”
  • “test the release build locally”
  • “install a release build for testing”
  • “/bump-version-dev”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Pre-flight
  2. Determine the next version
  3. Confirm with the user
  4. Run the dev-install script
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 3cd5070. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bump Version Dev loads about 1k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 469 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~121
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from lycorp-jp/sim-use at commit 3cd5070, republished under its Apache-2.0 licence (© lycorp-jp). 469 words, ~1,012 tokens.

Download SKILL.mdSave it as .claude/skills/bump-version-dev/SKILL.md (or your agent's skills folder).
name
bump-version-dev
description
Build a release-shaped sim-use binary and install it locally for testing. Use when the user runs `/bump-version-dev` or asks to "build a dev release", "test the release build locally", "install a release build for testing", or "prepare a release candidate without publishing". Builds APK + CLI, stages, ad-hoc signs, and repoints the PATH binary. Does NOT commit, tag, push, create releases, or update homebrew. After local validation, run `/release` to ship for real.

This skill builds and locally installs a release-shaped sim-use binary so the user can validate it before publishing. It delegates the heavy lifting to scripts/dev-install.sh and handles version determination + user confirmation.

Run from the sim-use repo root (git rev-parse --show-toplevel).

Restore flow

If the user passes restore as an argument (e.g. /bump-version-dev restore), skip everything and run:

bash
scripts/dev-install.sh --restore

Report success or failure and stop.

Step 1: Pre-flight

Run these checks. Abort with a clear error if any fails.

  1. Current directory is the sim-use repo root.
  2. build_products/Frameworks/ exists. If missing, tell the user to run scripts/build.sh dev (~30 min). Do NOT run it automatically.
  3. Android bridge toolchain: scripts/build-bridge.sh --check succeeds. If not, surface the missing tool.

Unlike /release, this skill does NOT require:

  • Clean working tree (local modifications are fine — this is a dev build)
  • GitHub auth
  • Homebrew tap clone
  • Codesign identity or notary profile

Step 2: Determine the next version

  1. Find the latest sim-use tag: git tag --list 'v*' --sort=-v:refname | head -1.
  2. If a prior tag exists, read commits since it: git log <last-tag>..HEAD --pretty=format:'%h %s'.
  3. Pick bump type from conventional commit prefixes:
    • feat!: / BREAKING CHANGE → major
    • feat: → minor
    • Only fix: / chore: / docs: / refactor: / test: → patch
  4. Compute the next version.

If the user specified a version (e.g. /bump-version-dev 0.9.1), use that verbatim instead of auto-bumping.

Step 3: Confirm with the user

Show:

  • The current tag and the target version.
  • The commit list since the last tag (one line each).
  • What will happen: "Build APK + CLI as vX.Y.Z, stage, ad-hoc sign, and replace the PATH binary."

Ask: "Build and install vX.Y.Z locally?" Wait for explicit yes/no/version override.

Show full SKILL.md (197 more words)Show less

Step 4: Run the dev-install script

bash
scripts/dev-install.sh --version X.Y.Z

This script handles:

  1. Rebuilding the Android bridge APK (scripts/build-bridge.sh)
  2. Building the universal CLI with SIM_USE_VERSION=X.Y.Z (scripts/build.sh executable)
  3. Staging the payload (scripts/release-artifacts.sh stage-build-output + verify-stage)
  4. Ad-hoc codesigning the staged payload
  5. Backing up the current PATH binary target
  6. Symlinking the PATH binary to the staged build
  7. Verifying sim-use --version

The script typically takes 2-5 minutes. Stream the output so the user sees progress. If the script fails, diagnose:

  • Bridge build failed → JDK/SDK issue, see CLAUDE.md Android pitfalls
  • verify-stage failed → missing resource bundle, re-check build output
  • Codesign failed → unlikely for ad-hoc; check macOS version
  • Symlink failed → permission issue on the install path

Step 5: Report

After the script succeeds, report:

  • The installed version (sim-use --version)
  • The symlink target
  • Reminder: test the build, then run /release to ship for real
  • Reminder: run scripts/dev-install.sh --restore (or /bump-version-dev restore) to go back

Things to NOT do

  • Don't modify CHANGELOG.md, bridge/app/build.gradle.kts, or any tracked file.
  • Don't commit, tag, or push anything.
  • Don't run --build-frameworks — that's a slow path requiring explicit user opt-in.
  • Don't codesign with Developer ID — ad-hoc is sufficient for local testing.
  • Don't create tarballs, formulas, or releases.
  • Don't attempt notarization.

© lycorp-jp, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/bump-version-dev of lycorp-jp/sim-use.

Open the folder on GitHubat commit 3cd5070

Compare with similar skills

Bump Version Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bump Version Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bump Version Dev this skilllycorp-jp/sim-use1.4k—~1kAutomated safety check: PassApache-2.0
Releasevaayne/mori303—~1.2kAutomated safety check: PassMIT
Deploy Androidtimusus/Shuttle2229—~1.2kAutomated safety check: PassApache-2.0
ReleaseHedvigInsurance/android154—~546Automated safety check: PassAGPL-3.0
Flutter Appccplugins/awesome-claude-code-plugins967—~1.1kAutomated safety check: NotesApache-2.0
Deploy iOStimusus/Shuttle2229—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Release

    vaayne/mori

    Release workflow for Mori macOS workspace terminal and MoriRemote iOS app.

    303 GitHub stars~1.2k tokensUpdated 2 mo ago
    MobileAuto-check passed

  • Deploy Android

    timusus/Shuttle2

    Deploy the Android app to the Play Store via GitHub Actions.

    229 GitHub stars~1.2k tokensUpdated yesterday
    MobileAuto-check passed

  • Release

    HedvigInsurance/android

    Cut a production release of the Android app (git flow release, version bump, push to trigger the Play Store upload).

    154 GitHub stars~546 tokensUpdated today
    MobileAuto-check passed

  • Flutter App

    ccplugins/awesome-claude-code-plugins

    Bootstrap a new Flutter mobile app with clean architecture, Riverpod, FVM-pinned SDK, current packages, and no deprecated APIs.

    967 GitHub stars~1.1k tokensUpdated 1 mo ago
    MobileAuto-check: notes

  • Deploy iOS

    timusus/Shuttle2

    Deploy Shuttle Music for iOS to TestFlight from this Mac. An agent skill from timusus/Shuttle2.

    229 GitHub stars~1.1k tokensUpdated yesterday
    MobileAuto-check passed

  • Android Readme Screenshot Studio

    permissionlesstech/bitchat-android

    Create or refresh polished, high-resolution screenshots of the Bitchat Android app for README and repository showcase use.

    7.7k GitHub stars~3k tokensUpdated yesterday
    MobileAuto-check passed

More from lycorp-jp/sim-use

  • Sim Use

    lycorp-jp/sim-use

    Drive iOS Simulator, Android emulator/device, and physical iPhone/iPad screens for AI agents.

    1.4k GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed

  • Release

    lycorp-jp/sim-use

    Cut a sim-use release end-to-end. An agent skill from lycorp-jp/sim-use.

    1.4k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Run Evals

    lycorp-jp/sim-use

    Prepare the environment and run the LLM-driven agent evals (e2e/agent-evals/) against a chosen sim-use binary.

    1.4k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Bump Version Dev

What does Bump Version Dev do?

Build a release-shaped sim-use binary and install it locally for testing. Bump Version Dev is an agent skill from lycorp-jp/sim-use. Build a release-shaped sim-use binary and install it locally for testing.

When should I use Bump Version Dev?

Bump Version Dev fits situations like: the user runs /bump-version-dev; asks to build a dev release; test the release build locally; install a release build for testing.

How do I install Bump Version Dev in Claude Code?

Run `npx skills add lycorp-jp/sim-use --skill bump-version-dev -a claude-code`. Or copy the skill folder (.agents/skills/bump-version-dev in lycorp-jp/sim-use) into .claude/skills/bump-version-dev in your project. Claude Code loads it when a task matches its description.

How do I install Bump Version Dev in Codex?

Run `npx skills add lycorp-jp/sim-use --skill bump-version-dev -a codex`. Or copy the skill folder (.agents/skills/bump-version-dev in lycorp-jp/sim-use) into .agents/skills/bump-version-dev in your project. Codex loads it when a task matches its description.

Can I use Bump Version Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lycorp-jp/sim-use --skill bump-version-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bump-version-dev, .gemini/skills/bump-version-dev, .github/skills/bump-version-dev and .opencode/skills/bump-version-dev in your project.

What does Bump Version Dev need to run?

Going by SKILL.md and its folder, Bump Version Dev needs the command-line tools its instructions call (git).

Does Bump Version Dev access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bump Version Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bump Version Dev use?

Bump Version Dev is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bump Version Dev use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bump Version Dev?

Skills that share tags, products or a category with Bump Version Dev: Release (vaayne/mori, 303 stars), Deploy Android (timusus/Shuttle2, 229 stars), Release (HedvigInsurance/android, 154 stars) and Flutter App (ccplugins/awesome-claude-code-plugins, 967 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bump Version Dev?

lycorp-jp (a GitHub organization) maintains it in lycorp-jp/sim-use, which has 1,393 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

Source: lycorp-jp/sim-use on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.