Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
← Back to list

Version Release (semantic versioning workflow)

Picks the correct semver bump for a change set and synchronizes every version surface in the repo plus the matching GitHub milestone.

Dev & CodingAdvanced★ 1,063⑂ 248AI score 8/10Last updated: Oct 11, 2026

What it does

  • Classifies a change set as patch / minor / major with explicit criteria, prefers the higher bump when ambiguous, and honors an explicit user-requested version instead of silently substituting one.
  • Updates every version-carrying surface in order: root and desktop packages/lockfiles, OpenAPI example plus regenerated openapi.yaml, docker-compose.yml image tags, Helm version/appVersion, all deployments/kubernetes/** labels, images and kustomize newTag, deploy.sh, deployment guides, CITATION.cff, and the UI build v<version> snapshot.
  • Treats server/__tests__/release-version-consistency.test.js as the machine-checkable release contract — read before, run after — and sweeps the old version string with grep -F (dots would otherwise act as regex wildcards).
  • Handles GitHub milestone bookkeeping with gh: query all milestones, create or reuse v<version>, stop on closed/duplicate matches, assign the PR and every linked closing issue, then re-read to verify.
  • Lists explicit do-nots: independently versioned client, mcp, monitoring, vscode-extension packages, service worker cache generations, Helm tag: "", blanket find-and-replace, and creating/moving tags without approval.

Who it's for

  • Monorepo maintainers whose version string lives in code, charts, manifests and docs at once.
  • Teams that want release paperwork (milestones, linked issues, consistency checks) automated rather than remembered.
  • CCAM users directly, or anyone adapting this checklist as a template for their own release process.

Examples

  1. "This PR adds a new dashboard page" → classified as minor with reasoning, then packages, Helm, Kubernetes tags and docs updated and the consistency test run.
  2. "Only a dependency security patch" → classified as patch, followed by a grep -F sweep confirming zero leftover hits outside lockfile history.
  3. "Sort out the release milestone" → queries all milestones, reuses an open v2.1.0, or halts and reports if it is closed or duplicated.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/hoangsonww/Claude-Code-Agent-Monitor/HEAD/.agents/skills/version-release/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .agents/skills/version-release folder from the GitHub repo hoangsonww/Claude-Code-Agent-Monitor into my ~/.claude/skills/version-release/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git /tmp/ccam && mkdir -p ~/.claude/skills && cp -r /tmp/ccam/.agents/skills/version-release ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repository into a temp directory: git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git /tmp/ccam
  3. Create the skills directory: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r /tmp/ccam/.agents/skills/version-release ~/.claude/skills/
  5. Confirm references/version-checklist.md came along with it.
  6. Install and authenticate GitHub CLI: run gh --version, then gh auth status (required for the milestone steps).
  7. Restart Claude Code and ask something like "prepare a release and bump the version".
  8. For other repositories, edit the file paths, image tags and test path inside SKILL.md to match your own layout.