Agent skill

Bump Release Version

Prepare OpenGameInstaller application releases by deciding whether to bump only application/package.json or also updater/package.json, then commit and create the annotated v{application-version} tag.

AGPL-3.0Auto-check passedDevelopment

Install Bump Release Version

skills CLI

$ npx skills add Nat3z/OpenGameInstaller --skill bump-release-version -a claude-code

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

GitHub CLI

$ gh skill install Nat3z/OpenGameInstaller bump-release-version --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/Nat3z/OpenGameInstaller.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bump-release-version .claude/skills/bump-release-version && 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/

Paste into Claude Code

Install the "bump-release-version" agent skill from https://github.com/Nat3z/OpenGameInstaller/tree/main/.agents/skills/bump-release-version into .claude/skills/bump-release-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-release-version", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Nat3z/OpenGameInstaller/tree/main/.agents/skills/bump-release-version

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Nat3z/OpenGameInstaller --skill bump-release-version -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Nat3z/OpenGameInstaller bump-release-version --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Nat3z/OpenGameInstaller.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/bump-release-version .agents/skills/bump-release-version && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "bump-release-version" agent skill from https://github.com/Nat3z/OpenGameInstaller/tree/main/.agents/skills/bump-release-version into .agents/skills/bump-release-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-release-version", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Nat3z/OpenGameInstaller --skill bump-release-version -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Nat3z/OpenGameInstaller bump-release-version --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Nat3z/OpenGameInstaller.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/bump-release-version .cursor/skills/bump-release-version && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "bump-release-version" agent skill from https://github.com/Nat3z/OpenGameInstaller/tree/main/.agents/skills/bump-release-version into .cursor/skills/bump-release-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-release-version", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Nat3z/OpenGameInstaller.git --path .agents/skills/bump-release-version

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Nat3z/OpenGameInstaller --skill bump-release-version -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Nat3z/OpenGameInstaller bump-release-version --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Nat3z/OpenGameInstaller.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/bump-release-version .gemini/skills/bump-release-version && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "bump-release-version" agent skill from https://github.com/Nat3z/OpenGameInstaller/tree/main/.agents/skills/bump-release-version into .gemini/skills/bump-release-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-release-version", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Nat3z/OpenGameInstaller bump-release-version

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Nat3z/OpenGameInstaller --skill bump-release-version -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Nat3z/OpenGameInstaller.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/bump-release-version .github/skills/bump-release-version && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "bump-release-version" agent skill from https://github.com/Nat3z/OpenGameInstaller/tree/main/.agents/skills/bump-release-version into .github/skills/bump-release-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-release-version", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Nat3z/OpenGameInstaller --skill bump-release-version -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Nat3z/OpenGameInstaller bump-release-version --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Nat3z/OpenGameInstaller.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/bump-release-version .opencode/skills/bump-release-version && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "bump-release-version" agent skill from https://github.com/Nat3z/OpenGameInstaller/tree/main/.agents/skills/bump-release-version into .opencode/skills/bump-release-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-release-version", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: bump-release-version
GitHub stars: 118
Token cost: ~745 tokens
SKILL.md length: 358 words
Files: 2
Skills in repo: 1
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Prepare OpenGameInstaller application releases by deciding whether to bump only application/package.json or also updater/package.json, then commit and create the annotated v{application-version} tag.

Works in 5 steps: Read application/package.json and… → Check git status, existing v* tags, and… → Find the commit that introduced the… → …
Release/version/tag requests in this repository
SKILL.md covers Inspect the release scope, Decide versions and Apply the release
Calls git

What it does

Bump Release Version is an agent skill from Nat3z/OpenGameInstaller. Prepare OpenGameInstaller application releases by deciding whether to bump only application/package.json or also updater/package.json, then commit and create the annotated v{application-version} tag. Use for release/version/tag requests in this repository, especially when deciding whether the independently versioned updater changed.

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development. It works with npm and Git. The repository describes itself as: a game installation and management platform built with developers in mind. The licence is AGPL-3.0.

When your agent uses it

Release/version/tag requests in this repository
Especially when deciding whether the independently versioned updater changed

Example prompts

“/bump-release-version”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Read application/package.json and updater/package.json.
Check git status, existing v* tags, and the diff since the latest application release tag.
Find the commit that introduced the current updater version
Inspect committed and working-tree changes after that commit that can alter the updater artifact
State the decision and evidence before editing.

What it can do on your machine

Read from SKILL.md and the folder at commit 17eb006. 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 Release Version loads about 745 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 358 words of instructions outside code blocks.

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

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 Nat3z/OpenGameInstaller at commit 17eb006, republished under its AGPL-3.0 licence (© Nat3z). 358 words, ~745 tokens.

Download SKILL.mdSave it as .claude/skills/bump-release-version/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: bump-release-version
description: Prepare OpenGameInstaller application releases by deciding whether to bump only application/package.json or also updater/package.json, then commit and create the annotated v{application-version} tag. Use for release/version/tag requests in this repository, especially when deciding whether the independently versioned updater changed.

Bump Release Version

Treat the application and updater as independently versioned release artifacts. The v* Git tag follows the application version; it does not imply that the updater version must change.

Inspect the release scope

Read application/package.json and updater/package.json.
Check git status, existing v* tags, and the diff since the latest application release tag.
Find the commit that introduced the current updater version:
bash
```
git log -1 -G'"version":' --format=%H -- updater/package.json
```
Inspect committed and working-tree changes after that commit that can alter the updater artifact:
- updater/**, excluding a version-only change already made for this release
- packages imported by updater; currently packages/logger/**
- root dependency or lockfile changes only when they change dependencies bundled into updater
State the decision and evidence before editing.

Do not bump the updater merely because the release workflow rebuilds it, the application changed, a new application tag is created, or release/CI documentation changed.

Decide versions

Always bump application/package.json for a new v* application release.
Bump updater/package.json only when the inspection finds an unreleased updater-artifact change, or the user explicitly requests it.
If the updater version was already bumped after its artifact changes, keep it as-is rather than bumping twice.
Default to a patch bump. Honor an explicit version or semver level from the user.
Never force the two package versions to match.

When evidence is ambiguous, explain the specific file and why it may affect the packaged updater. Ask only if choosing incorrectly could publish a changed updater under an old version.

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

Apply the release

Edit only the selected package version fields. Preserve unrelated working-tree changes.
Do not update other package versions. Do not regenerate bun.lock for a version-only bump unless the user explicitly asks for lockfile synchronization.
Verify git diff --check and inspect the complete diff.
Commit only the intended version files using:
- application only: chore(application): bump version to X.Y.Z
- application and updater: chore(release): bump application and updater versions
Create an annotated vX.Y.Z tag on that commit, where X.Y.Z is the application version. Use the user's release description exactly as the tag message.
Verify the commit, tag target, tag contents, and clean/expected worktree state.

Do not push unless the user asks.

Files

SKILL.md and 1 other file in .agents/skills/bump-release-version of Nat3z/OpenGameInstaller.

SKILL.md
agents/openai.yaml

Open the folder on GitHubat commit 17eb006

Compare with similar skills

Bump Release Version 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 Release Version compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Bump Release Version this skillNat3z/OpenGameInstaller	118	—	~745	Automated safety check: Pass	AGPL-3.0	today
Migrate Internal Package into GhostTryGhost/Ghost	56k	—	~3.8k	Automated safety check: Pass	MIT	today
Open Code Review CLIalibaba/open-code-review	45k	—	~3.1k	Automated safety check: Pass	Apache-2.0	yesterday
Open Code Review Delegatealibaba/open-code-review	45k	—	~2k	Automated safety check: Pass	Apache-2.0	yesterday
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	today
Hunk Release Workflowmodem-dev/hunk	9.6k	—	~3.8k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
56k GitHub stars~3.8k tokensUpdated today
DevelopmentAuto-check passed
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
45k GitHub stars~3.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Open Code Review Delegate
alibaba/open-code-review
Has the host agent do the code review itself while the ocr CLI handles file selection and rule lookup, covering workspace changes, branch ranges or single commits.
45k GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
18k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.6k GitHub stars~3.8k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Code Review
yaklang/yakit
对 Yakit 仓库的代码改动做规范化 code review：按代码逻辑、TS 定义、UI 引用与 Props、CSS 样式、依赖版本、配置项六个维度审查，检查测试用例缺失，强制执行 tsc 类型检查与 vitest 测试验证，输出「结果汇总 / 明细解释 / 合并结论」三块报告，经用户确认后写入文件。当用户要求 review、审查、评审代码改动，或在提交、合并、提 PR…
7.8k GitHub stars~1.5k tokensUpdated today
DevelopmentAuto-check: notes

Works with

Questions about Bump Release Version

What does Bump Release Version do?

Prepare OpenGameInstaller application releases by deciding whether to bump only application/package.json or also updater/package.json, then commit and create the annotated v{application-version} tag. Bump Release Version is an agent skill from Nat3z/OpenGameInstaller.json, then commit and create the annotated v{application-version} tag.

When should I use Bump Release Version?

Bump Release Version fits situations like: release/version/tag requests in this repository; especially when deciding whether the independently versioned updater changed.

How do I install Bump Release Version in Claude Code?

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

How do I install Bump Release Version in Codex?

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

Can I use Bump Release Version 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 Nat3z/OpenGameInstaller --skill bump-release-version -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-release-version, .gemini/skills/bump-release-version, .github/skills/bump-release-version and .opencode/skills/bump-release-version in your project.

What does Bump Release Version need to run?

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

Does Bump Release Version 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 Release Version 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 Release Version use?

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

How many tokens does Bump Release Version use?

About 745 tokens (SKILL.md is roughly 3k 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 Release Version?

Skills that share tags, products or a category with Bump Release Version: Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars), Open Code Review CLI (alibaba/open-code-review, 45k stars), Open Code Review Delegate (alibaba/open-code-review, 45k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bump Release Version?

Nat3z (a GitHub user) maintains it in Nat3z/OpenGameInstaller, which has 118 GitHub stars. The repository was last updated on October 9, 2026.

Source: Nat3z/OpenGameInstaller on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Bump Release Version

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Bump Release Version

Inspect the release scope

Decide versions

Apply the release

Files

Compare with similar skills

Similar skills

Migrate Internal Package into Ghost

Open Code Review CLI

Open Code Review Delegate

Verdaccio Pull Request Workflow

Hunk Release Workflow

Code Review

Related

Questions about Bump Release Version