How do I install the Version Updates skill?

Run npx skillmds@latest add majiayu000/version-updates-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Version Updates safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Version Updates?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Version Updates free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Version Updates?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Version Updates by majiayu000 — Agent Skill

Name: Version Updates
Rating: 4.2 (5 reviews)
Author: majiayu000

Version Updates

Bump project versions across configs, docs, and changelog using git-workspace-review context. Triggers: version bump, semver, release version, changelog update, version update, package version, release preparation Use when: bumping project versions, updating changelogs, preparing releases, coordinating version changes across files DO NOT use when: just documentation updates - use doc-updates. DO NOT use when: full PR preparation - use pr-prep. Use this skill for version management and release preparation.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

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.

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`)

List configuration files that store the version (e.g., Cargo.toml, package.json, pyproject.toml).
Include changelog and README references that mention the version.

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

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.

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.

---name: version-updates-2description: Bump project versions across configs, docs, and changelog using git-workspace-review context. Triggers: version bump, semver, release version, changelog update, version update, package version, release preparation Use when: bumping project versions, updating changelogs, preparing releases, coordinating version changes across files DO NOT use when: just documentation updates - use doc-updates. DO NOT use when: full PR preparation - use pr-prep. Use this skill for version management and release preparation.--- # 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. ## Required TodoWrite Items 1. `version-update:context-collected` 2. `version-update:target-files` 3. `version-update:version-set` 4. `version-update:docs-updated` 5. `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`) - List configuration files that store the version (e.g., `Cargo.toml`, `package.json`, `pyproject.toml`). - Include changelog and README references that mention the version. ## Step 3: Update Versions (`version-set`) - 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. ## 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.

Frequently asked questions