Agent skill

Version Updates

Bumps versions, updates changelogs, and coordinates version changes across files for releases.

MITAuto-check passedDevelopment

Install Version Updates

skills CLI

$ npx skills add athola/claude-night-market --skill version-updates -a claude-code

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

GitHub CLI

$ gh skill install athola/claude-night-market version-updates --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/athola/claude-night-market.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/sanctum/skills/version-updates .claude/skills/version-updates && 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 "version-updates" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/version-updates into .claude/skills/version-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-updates", 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/athola/claude-night-market/tree/master/plugins/sanctum/skills/version-updates

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 athola/claude-night-market --skill version-updates -a codex

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

GitHub CLI

$ gh skill install athola/claude-night-market version-updates --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/sanctum/skills/version-updates .agents/skills/version-updates && 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 "version-updates" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/version-updates into .agents/skills/version-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-updates", 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 athola/claude-night-market --skill version-updates -a cursor

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

GitHub CLI

$ gh skill install athola/claude-night-market version-updates --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/sanctum/skills/version-updates .cursor/skills/version-updates && 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 "version-updates" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/version-updates into .cursor/skills/version-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-updates", 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/athola/claude-night-market.git --path plugins/sanctum/skills/version-updates

--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 athola/claude-night-market --skill version-updates -a gemini-cli

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

GitHub CLI

$ gh skill install athola/claude-night-market version-updates --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/athola/claude-night-market.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/sanctum/skills/version-updates .gemini/skills/version-updates && 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 "version-updates" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/version-updates into .gemini/skills/version-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-updates", 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 athola/claude-night-market version-updates

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 athola/claude-night-market --skill version-updates -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/sanctum/skills/version-updates .github/skills/version-updates && 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 "version-updates" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/version-updates into .github/skills/version-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-updates", 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 athola/claude-night-market --skill version-updates -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 athola/claude-night-market version-updates --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/sanctum/skills/version-updates .opencode/skills/version-updates && 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 "version-updates" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/sanctum/skills/version-updates into .opencode/skills/version-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-updates", 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: version-updates
GitHub stars: 342
Token cost: ~1.2k tokens
SKILL.md length: 464 words
Files: 1
Skills in repo: 159
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Bumps versions, updates changelogs, and coordinates version changes across files for releases.

Works in 5 steps: Collect Context (context-collected) → Identify Targets (target-files) → Update Versions (version-set) → …
Preparing a release
SKILL.md covers When To Use, When NOT To Use, Required TodoWrite Items and Step 1: Collect Context…, plus 6 more sections
Calls git, cargo and npm

What it does

Version Updates is an agent skill from athola/claude-night-market. Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.

Its SKILL.md is about 1.2k 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 Development, covering Changelog and release notes. It works with Rust and npm. The repository describes itself as: 23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context… The licence is MIT.

When your agent uses it

Preparing a release
Bumping the project version

Example prompts

“Use the version-updates skill to bump versions, updates changelogs, and coordinates version changes across files for releases”
“/version-updates”

Workflow steps

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

Collect Context (context-collected)
Identify Targets (target-files)
Update Versions (version-set)
Update Documentation (docs-updated)
Verification (verification)

What it can do on your machine

Read from SKILL.md and the folder at commit 9f3eb00. 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
- cargo
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and npm, 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

Version Updates loads about 1.2k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 464 words of instructions outside code blocks.

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

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 athola/claude-night-market at commit 9f3eb00, republished under its MIT licence (© athola). 464 words, ~1,171 tokens.

Download SKILL.mdSave it as .claude/skills/version-updates/SKILL.md (or your agent's skills folder).

name: version-updates
description: Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.
alwaysApply: false
category: artifact-generation
tags: version, release, changelog, semver, bump
complexity: medium
model_hint: standard
estimated_tokens: 700
dependencies: sanctum:git-workspace-review

Version Update Workflow

When To Use

Use this skill when preparing a release or bumping the project version. Run Skill(sanctum:git-workspace-review) first to capture current changes.

When NOT To Use

Just documentation updates - use doc-updates
Full PR preparation - use pr-prep

Required TodoWrite Items

version-update:context-collected
version-update:target-files
version-update:version-set
version-update:docs-updated
version-update:verification

Step 1: Collect Context (`context-collected`)

Confirm which version to apply (default: bump patch).
If the prompt provides an explicit version, note it.
validate Skill(sanctum:git-workspace-review) has already captured the repository status.

Step 2: Identify Targets (`target-files`)

Find ALL configuration files that store versions using recursive search:
- Root level: Cargo.toml, package.json, pyproject.toml
- Nested directories: Use glob to find */pyproject.toml, */Cargo.toml, */package.json
- Example: plugins/memory-palace/pyproject.toml must be included
- Exclude virtual environments (.venv, node_modules, target/) using grep -v
Include changelog and README references that mention the version.
Use: find plugins -name "pyproject.toml" -o -name "Cargo.toml" | grep -v ".venv"

Step 3: Update Versions (`version-set`)

Automated approach: Use plugins/sanctum/scripts/update_versions.py <version> to update all version files
- Supports pyproject.toml, Cargo.toml, package.json
- Automatically excludes virtual environments
- Finds nested version files (e.g., plugins/memory-palace/pyproject.toml)
- Use --dry-run flag first to preview changes
Manual approach: Update each target file with the new version
- For semantic versions, follow MAJOR.MINOR.PATCH or the specified format
- If the project supports multiple packages, document each update

Step 4: Update Documentation (`docs-updated`)

Add or update changelog entries with today's date.
Refresh README and docs references to mention the new version and any release notes.

Critical Documentation Files with Version References

These files contain version numbers and MUST be checked during version bumps:

File	Content
`docs/api-overview.md`	Plugin inventory table with all plugin versions
`CHANGELOG.md`	Version history and release notes
`book/src/reference/capabilities-reference.md`	May reference version-specific features
Plugin READMEs	May mention plugin versions

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

Scan for Additional Version References

bash

# Find all docs mentioning the OLD version
grep -r "1\.2\.6" docs/ book/ --include="*.md" | grep -v node_modules

# Common patterns to search:
# - "v1.2.6", "1.2.6", "(v1.2.6)"
# - Version tables in markdown
# - "Added in X.Y.Z" annotations

Update Sequence

Update config files (pyproject.toml, plugin.json, etc.) - automated
Update CHANGELOG.md - add new version section
Update docs/api-overview.md - update version table and plugin details
Scan for other version references and update as needed

Step 5: Verification (`verification`)

Run relevant builds or tests if version bumps require them (e.g., cargo test, npm test).
Show git status -sb and git diff excerpts to confirm the version bumps.

Output Instructions

Summarize the files changed and the new version number.
Mention follow-up steps, such as publishing or tagging, if applicable.

Exit Criteria

All 5 TodoWrite items (version-update:context-collected through version-update:verification) are created before any file is modified and marked complete in order
update_versions.py --dry-run <version> run first and its output reviewed before any version file is written
Version bumped consistently across all found config files (pyproject.toml, Cargo.toml, package.json, plugin.json) with no target file missing the update
CHANGELOG.md updated with a new version section dated today
git diff output confirms version changes in all identified target files; a summary of files changed and new version number is reported to the user

Files

Just SKILL.md in plugins/sanctum/skills/version-updates of athola/claude-night-market.

Open the folder on GitHubat commit 9f3eb00

Compare with similar skills

Version Updates 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.

Version Updates compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Version Updates this skillathola/claude-night-market	342	—	~1.2k	Automated safety check: Pass	MIT	2 days ago
Leanspec Developmentcodervisor/leanspec	296	—	~2.5k	Automated safety check: Pass	MIT	4 mo ago
Lime Release Workflowlimecloud/lime	1.5k	—	~1.8k	Automated safety check: Pass	None	today
Prepare Releaseayutaz/piper-plus	220	—	~2k	Automated safety check: Pass	MIT	today
Release Prepayutaz/piper-plus	220	—	~1.6k	Automated safety check: Pass	MIT	today
Dev BumpNetis/heron	102	—	~983	Automated safety check: Pass	Apache-2.0	3 days ago

Similar skills

Leanspec Development
codervisor/leanspec
Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec.
296 GitHub stars~2.5k tokensUpdated 4 mo ago
DevelopmentAuto-check passed
Lime Release Workflow
limecloud/lime
准备并执行 Lime 发版；覆盖版本号、发布说明、产物清理、验证门禁、commit、tag 和推送. An agent skill from limecloud/lime.
1.5k GitHub stars~1.8k tokensUpdated today
DevelopmentAuto-check passed
Prepare Release
ayutaz/piper-plus
9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、実 bump 差分の markdown 提案 + 順序付き…
220 GitHub stars~2k tokensUpdated today
DevelopmentAuto-check passed
Release Prep
ayutaz/piper-plus
7 ランタイム manifest の version 一覧表示、CHANGELOG [Unreleased] → [X.Y.Z] 移行支援、公開 registry の最新公開 version 確認を 1 コマンドで実行する read-mostly skill。docs/spec/release-versions.toml を canonical source として参照。
220 GitHub stars~1.6k tokensUpdated today
DevelopmentAuto-check passed
Dev Bump
Netis/heron
Bump Heron version via the VERSION-file SSOT. An agent skill from Netis/heron.
102 GitHub stars~983 tokensUpdated 3 days ago
AI & LLM EngineeringAuto-check passed
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
38k GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check passed

Questions about Version Updates

What does Version Updates do?

Bumps versions, updates changelogs, and coordinates version changes across files for releases. Version Updates is an agent skill from athola/claude-night-market. Bumps versions, updates changelogs, and coordinates version changes across files for releases.

When should I use Version Updates?

Version Updates fits situations like: preparing a release; bumping the project version.

How do I install Version Updates in Claude Code?

Run `npx skills add athola/claude-night-market --skill version-updates -a claude-code`. Or copy the skill folder (plugins/sanctum/skills/version-updates in athola/claude-night-market) into .claude/skills/version-updates in your project. Claude Code loads it when a task matches its description.

How do I install Version Updates in Codex?

Run `npx skills add athola/claude-night-market --skill version-updates -a codex`. Or copy the skill folder (plugins/sanctum/skills/version-updates in athola/claude-night-market) into .agents/skills/version-updates in your project. Codex loads it when a task matches its description.

Can I use Version Updates 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 athola/claude-night-market --skill version-updates -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/version-updates, .gemini/skills/version-updates, .github/skills/version-updates and .opencode/skills/version-updates in your project.

What does Version Updates need to run?

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

Does Version Updates access the network?

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

Is Version Updates 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 Version Updates use?

Version Updates is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Version Updates use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 Version Updates?

Skills that share tags, products or a category with Version Updates: Leanspec Development (codervisor/leanspec, 296 stars), Lime Release Workflow (limecloud/lime, 1.5k stars), Prepare Release (ayutaz/piper-plus, 220 stars) and Release Prep (ayutaz/piper-plus, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Version Updates?

athola (a GitHub user) maintains it in athola/claude-night-market, which has 342 GitHub stars. The repository holds 159 skills in this directory. The repository was last updated on October 6, 2026.

Source: athola/claude-night-market on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Version Updates

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

Version Update Workflow

When To Use

When NOT To Use

Required TodoWrite Items

Step 1: Collect Context (context-collected)

Step 2: Identify Targets (target-files)

Step 3: Update Versions (version-set)

Step 4: Update Documentation (docs-updated)

Critical Documentation Files with Version References

Scan for Additional Version References

Update Sequence

Step 5: Verification (verification)

Output Instructions

Exit Criteria

Files

Compare with similar skills

Similar skills

More from athola/claude-night-market

Related

Questions about Version Updates

Step 1: Collect Context (`context-collected`)

Step 2: Identify Targets (`target-files`)

Step 3: Update Versions (`version-set`)

Step 4: Update Documentation (`docs-updated`)

Step 5: Verification (`verification`)