New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Version Release

by hoangsonww in hoangsonww/Claude-Code-Agent-Monitor

Choose and apply the correct semantic version bump for this repository.

MITAuto-check passedDevOps & Cloud

Install Version Release

skills CLI
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a claude-code

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

GitHub CLI
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor version-release --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/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/version-release .claude/skills/version-release && 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/

Facts

Skill name
version-release
GitHub stars
1k
Token cost
~1.6k tokens
SKILL.md length
685 words
Files
3 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Choose and apply the correct semantic version bump for this repository.

  • Every user-visible release
  • SKILL.md covers Workflow, Authoritative surface list, GitHub milestone workflow and References
  • Calls gh, node and npm
  • Before merge when a change set should ship as patch

What it does

Version Release is an agent skill from hoangsonww/Claude-Code-Agent-Monitor. Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/version-checklist.md`).

It sits in DevOps & Cloud. The repository describes itself as: 🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity… The licence is MIT.

When your agent uses it

  • Every user-visible release
  • Before merge when a change set should ship as patch
  • Whenever package/plugin/desktop version metadata must stay synchronized

Example prompts

  • “/version-release”

Requirements

  • Docker

What it can do on your machine

Read from SKILL.md and the folder at commit e0f4a1a. 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:

    • gh
    • node
    • npm
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, npm and 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

Version Release loads about 1.6k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 685 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

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 hoangsonww/Claude-Code-Agent-Monitor at commit e0f4a1a, republished under its MIT licence (© hoangsonww). 685 words, ~1,564 tokens.

Download SKILL.mdSave it as .claude/skills/version-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
version-release
description
Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.

Version Release Skill

Apply Semantic Versioning across CCAM:

  • Patch (X.Y.Z+1): backward-compatible fixes, docs-only work, dependency/security maintenance, refactors, or small improvements without a substantial new capability.
  • Minor (X.Y+1.0): backward-compatible features or meaningfully larger capabilities such as new workflows, pages, integrations, API fields/routes, or major UX surfaces.
  • Major (X+1.0.0): breaking public behavior, removed or renamed contracts, required migrations, or fundamental product/architecture changes.

Choose the highest applicable category. If the boundary is ambiguous, prefer the higher bump or ask before release. Do not classify from diff size or commit count alone. An explicit user-requested version takes precedence over automatic classification. Record the override, synchronize that exact version, and do not silently substitute a different patch, minor, or major number.

Workflow

  • Explain the chosen bump from the current root version.
  • Update root and desktop package/lockfile versions.
  • Update the OpenAPI version example and regenerate openapi.yaml.
  • Update the deployment surface: docker-compose.yml image tags (ccam-dashboard, ccam-mcp), the Helm chart's version and appVersion, every deployments/kubernetes/** version label, image tag, and kustomize newTag, and deployments/scripts/deploy.sh (both the --tag example and the sed substitution).
  • Update the release shown in DEPLOYMENT.md, docs/DEPLOYMENT.md, and CITATION.cff.
  • Update version-sensitive UI snapshots; the dashboard renders UI build v<version>, so regenerate and confirm the diff is only that line.
  • Run npm run extensions:sync to regenerate Claude/Codex plugin manifests and both marketplaces.
  • Keep independently shipped client/MCP/monitoring/VS Code package versions unchanged unless explicitly included.
  • Create or reuse the exact open GitHub milestone v<version> for the new root version. Query all milestones first. If the exact title already exists closed or more than once, stop and resolve that release state instead of creating a duplicate.
  • Assign the current open pull request containing the bump to v<version>. Read its closingIssuesReferences and assign every linked closing issue to the same milestone. If no PR exists yet, leave this step explicitly incomplete until the PR is created.
  • Verify the PR and every linked issue report the expected milestone with fresh GitHub reads.
  • Run npm run extensions:validate, relevant tests/builds, and the CLI version check.
  • Never create or move a release tag without explicit user approval.
Show full SKILL.md (343 more words)Show less

Authoritative surface list

server/__tests__/release-version-consistency.test.js is the machine-checkable release contract. Read it before bumping and run it after:

bash
node --test server/__tests__/release-version-consistency.test.js

It covers root/desktop packages and lockfiles, live and generated OpenAPI, Compose and Helm, Kubernetes labels/images/kustomize tags, generated plugin manifests, both marketplaces, the deployment guides and deploy.sh, and the negative assertion that independently shipped subprojects were not dragged along.

Any new file carrying the release version needs an assertion added in the same change. An unasserted surface drifts silently — CITATION.cff sat at 1.1.0 across many releases for exactly this reason.

Before finishing, sweep for the previous version and expect zero hits outside lockfile history and deliberate historical references such as "pre-v2.0.9":

bash
previous_version="$(git show HEAD:package.json | node -p 'JSON.parse(require("fs").readFileSync(0,"utf8")).version')"
grep -rFn "$previous_version" --exclude-dir=node_modules --exclude-dir=.git \
  --exclude-dir=dist --exclude-dir=.worktrees .

grep -F matters: the dots in a version are regex wildcards otherwise, so a plain grep -r also matches unrelated strings like 2a0b11. Reading the previous value from HEAD:package.json keeps the command runnable as-is mid-bump, before the change is committed.

Do not bump: sw.js / client/public/sw.js cache generations (not release-tied; wiki/sw.js belongs to the docs skill), the Helm values.yaml tag: "" which falls back to appVersion, or the independently versioned client, mcp, monitoring, and vscode-extension packages.

Never blanket find-and-replace the version across the repo: it pulls in the independent subprojects and rewrites historical references.

GitHub milestone workflow

Run gh auth status first. Stop if the active account is not the intended identity for the repository.

bash
repo="$(gh repo view --json nameWithOwner --jq .nameWithOwner)"
version="$(node -p "require('./package.json').version")"
milestone="v${version}"
pr="$(gh pr view --json number --jq .number)"

existing="$(
  gh api "repos/${repo}/milestones?state=all&per_page=100" --paginate \
    --jq ".[] | select(.title == \"${milestone}\") | [.number, .state] | @tsv"
)"
  • Empty existing: create with gh api --method POST "repos/${repo}/milestones" -f title="${milestone}".
  • One open match: reuse it.
  • Closed or duplicate matches: stop. Do not create another release milestone.
  • Assign the PR with gh pr edit "$pr" --milestone "$milestone".
  • Read linked issues with gh pr view "$pr" --json closingIssuesReferences, then assign each same-repository issue with gh issue edit <number> --milestone "$milestone".
  • If a closing issue belongs to another repository, stop and report it. Milestones are repository-scoped, so do not mutate another repository implicitly.
  • Verify with gh pr view "$pr" --json milestone,closingIssuesReferences and fresh gh issue view <number> --json milestone calls.

Milestone creation and assignment are required release bookkeeping for a version bump. They do not authorize creating a Git tag or GitHub Release.

References

  • references/version-checklist.md

© hoangsonww, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/version-release of hoangsonww/Claude-Code-Agent-Monitor.

  • SKILL.md
  • agents/openai.yaml
  • references/version-checklist.md

Open the folder on GitHubat commit e0f4a1a

Compare with similar skills

Version Release 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 Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Version Release this skillhoangsonww/Claude-Code-Agent-Monitor1k—~1.6kAutomated safety check: PassMIT
KubeSphere Multi-Tenant Managementkubesphere/kubesphere17k—~3.1kAutomated safety check: PassCustom licence
Triage Codacynetdata/netdata81k—~2.2kAutomated safety check: NotesGPL-3.0
Azure PricingAzure/Copilot-Studio-and-Azure1103 repos~2.4kAutomated safety check: PassMIT
NGINX Ingress Policy CRD Guidenginx/kubernetes-ingress5.1k—~2kAutomated safety check: PassApache-2.0
ArvanCloud API Operatorerfnzdeh/arvancloud-agent-skill135—~3.9kAutomated safety check: PassMIT

Similar skills

  • KubeSphere Multi-Tenant Management

    kubesphere/kubesphere

    Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.

    17k GitHub stars~3.1k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Triage Codacy

    netdata/netdata

    Inspect, analyze, troubleshoot, or review Codacy findings and local analyzer/API helpers.

    81k GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Azure Pricing

    Azure/Copilot-Studio-and-Azure

    Official

    Fetches real-time Azure retail pricing using the Azure Retail Prices API (prices.azure.com) and estimates Copilot Studio agent credit consumption.

    110 GitHub starsUsed in 3 repos~2.4k tokens
    DevOps & CloudAuto-check passed

  • NGINX Ingress Policy CRD Guide

    nginx/kubernetes-ingress

    Step-by-step checklist for adding a new Policy CRD type to the NGINX Ingress Controller, from the Go types and validation to config generation and templates.

    5.1k GitHub stars~2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • ArvanCloud API Operator

    erfnzdeh/arvancloud-agent-skill

    Drives ArvanCloud's REST APIs for CDN, DNS, cloud servers, object storage and more, with helper scripts for calls, account inventory and certificates.

    135 GitHub stars~3.9k tokensUpdated 9 days ago
    DevOps & CloudAuto-check passed

  • Datadog Data Source Generator

    DataDog/terraform-provider-datadog

    Official

    Generates a Datadog Terraform provider data source from an OpenAPI operation with tfgen and opens a review-ready GitHub PR with a risk scan and testing guide.

    468 GitHub stars~2.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from hoangsonww/Claude-Code-Agent-Monitor

All 78 skills in this repo

  • Budget Set

    hoangsonww/Claude-Code-Agent-Monitor

    Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard.

    1k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

  • Cost Breakdown

    hoangsonww/Claude-Code-Agent-Monitor

    Break down Claude Code costs using the Agent Monitor pricing engine.

    1k GitHub starsUsed in 1 repo~845 tokens
    Auto-check passed

  • Hook Diagnostics

    hoangsonww/Claude-Code-Agent-Monitor

    Diagnose Claude Code hook installation, delivery, and ingestion issues.

    1k GitHub starsUsed in 1 repo~676 tokens
    Auto-check passed

  • Memory Review

    hoangsonww/Claude-Code-Agent-Monitor

    Review the file-based memory store via the Agent Monitor Config Explorer API: the user and project CLAUDE.md plus per-project auto-memory files under ~/.claude/projects/<slug/memory/.md.

    1k GitHub starsUsed in 1 repo~970 tokens
    Auto-check passed

  • Transcript Grep

    hoangsonww/Claude-Code-Agent-Monitor

    Search a Claude Code session transcript for a string or regex pattern and show every matching message with surrounding context.

    1k GitHub starsUsed in 1 repo~706 tokens
    Auto-check passed

  • Cache Efficiency

    hoangsonww/Claude-Code-Agent-Monitor

    Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (totalcacheread / (totalcacheread + totalinput)), cachewrite vs cacheread reuse, cache-read…

    1k GitHub stars~966 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Version Release

What does Version Release do?

Choose and apply the correct semantic version bump for this repository. Version Release is an agent skill from hoangsonww/Claude-Code-Agent-Monitor. Choose and apply the correct semantic version bump for this repository.

When should I use Version Release?

Version Release fits situations like: every user-visible release; before merge when a change set should ship as patch; whenever package/plugin/desktop version metadata must stay synchronized.

How do I install Version Release in Claude Code?

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

How do I install Version Release in Codex?

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

Can I use Version Release 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 hoangsonww/Claude-Code-Agent-Monitor --skill version-release -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-release, .gemini/skills/version-release, .github/skills/version-release and .opencode/skills/version-release in your project.

What does Version Release need to run?

Going by SKILL.md and its folder, Version Release needs the command-line tools its instructions call (gh, node, npm and git). Our summary lists: Docker.

Does Version Release access the network?

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

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

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

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 352 tokens, read only when the agent opens those files.

What are the alternatives to Version Release?

Skills that share tags, products or a category with Version Release: KubeSphere Multi-Tenant Management (kubesphere/kubesphere, 17k stars), Triage Codacy (netdata/netdata, 81k stars), Azure Pricing (Azure/Copilot-Studio-and-Azure, 110 stars) and NGINX Ingress Policy CRD Guide (nginx/kubernetes-ingress, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Version Release?

hoangsonww (a GitHub user) maintains it in hoangsonww/Claude-Code-Agent-Monitor, which has 1,049 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.

Source: hoangsonww/Claude-Code-Agent-Monitor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.