mcpbeat Sign in

Version Updates Skill for Claude

Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
324
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/athola/claude-night-market --skill version-updates

The instruction itself

14 sections, as written by the author

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/hooks/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/hooks/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 |

Scan for Additional Version References

# 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

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take athola/version-updates from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.