- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/HEAD/.claude/skills/version-releaseDo publicador
Use Semantic Versioning as the repository-wide release rule:
X.Y.Z+1) for backward-compatible bug fixes, documentation-only changes, dependency/security maintenance, internal refactors, and small user-visible improvements that do not create a substantial new capability.X.Y+1.0) for backward-compatible feature additions or meaningfully larger product capabilities, including new workflows, pages, integrations, API fields/routes, or major UX surfaces.X+1.0.0) for backward-incompatible behavior, removed/renamed public contracts, required migrations, or fundamental product/architecture changes.When a change fits more than one category, use the highest applicable bump. When uncertain between adjacent categories, prefer the higher bump or ask the user before releasing. Never infer the bump from commit count, diff size, or elapsed time alone. When the user explicitly requests a concrete version, that instruction overrides automatic classification. State the override and synchronize the requested version exactly.
Use the manual Prepare Release Bump workflow for routine releases. Its repository-specific input names are intentionally different from standard SemVer labels:
major increments the first component: X.Y.Z to X+1.0.0.intermediate increments the standard SemVer minor component: X.Y.Z to X.Y+1.0.minor increments the standard SemVer patch component: X.Y.Z to X.Y.Z+1.Preview the exact plan locally without writes:
node scripts/bump-release.js intermediate --dry-run --json
The workflow creates one branch, one coordinated commit, the exact open milestone, and one pull request. It also assigns that milestone to every merged default-branch PR that does not already have a milestone, including older omissions, while preserving existing assignments. Every automation-created commit ends with Co-authored-by: hoangsonww <[email protected]>. It requires the repository setting Allow GitHub Actions to create and approve pull requests, checks that prerequisite before remote writes, and keeps default workflow permissions read-only. It explicitly dispatches CI, file-header, and CLA checks because repository-token PR creation does not emit secondary workflow events. It never merges, force-pushes, tags, or publishes. Existing default-branch CI publishes only after a maintainer merges the PR.
package.json version and summarize why the change is patch, minor, or major.package.json and root lockfile.desktop/package.json and desktop/package-lock.json.server/openapi.js, then run npm run openapi:yaml.docker-compose.yml (ccam-dashboard and ccam-mcp image tags), deployments/helm/agent-monitor/Chart.yaml (version and appVersion), every deployments/kubernetes/** manifest (app.kubernetes.io/version labels, image: tags, kustomize newTag), and deployments/scripts/deploy.sh (the --tag example and the sed image substitution).DEPLOYMENT.md and docs/DEPLOYMENT.md (the ccam-dashboard:<version> substitution example) and in CITATION.cff (version:).UI build v<version>; regenerate with cd client && npx vitest run -u and confirm the diff is only the version line).npm run extensions:sync so every Claude/Codex plugin manifest and marketplace stays on the root release.v<version> for the new root version. Query all milestones before creating one. If an exact-title milestone already exists and is closed, stop and verify whether that version has already shipped instead of creating a duplicate.closingIssuesReferences from the PR and assign every linked closing issue to the same milestone. If the branch has no PR yet, create/reuse the milestone now and treat PR/issue assignment as an incomplete release step until the PR exists.server/__tests__/release-version-consistency.test.js is the machine-checkable
contract for a release bump. Read it first and run it last — it is more
reliable than this document, because it fails when a surface drifts:
node --test server/__tests__/release-version-consistency.test.js
It asserts root/desktop packages and lockfiles (including packages[""].version),
the live and generated OpenAPI versions, Compose and Helm metadata, Kubernetes
labels/images/kustomize tags, every generated plugin manifest, both marketplace
catalogs, the deployment guides and deploy.sh, and that the independently
versioned subprojects have not been dragged along.
When you add a new file that carries the release version, add an assertion there
in the same change. A surface with no assertion is a surface that will silently
drift — CITATION.cff sat at 1.1.0 for many releases for exactly this reason.
Cross-check with a repo-wide sweep for the previous version before finishing:
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.
Expect zero hits outside package-lock.json history and deliberate historical
references (for example "pre-v2.0.9 inflation" in the token-repair docs), which
must stay pointing at the release they describe.
sw.js and client/public/sw.js cache names (landing-v2, dashboard-v2)
are cache generations, not release versions. wiki/sw.js is bumped when wiki
content changes, which is the update-project-docs skill's job, not this one.deployments/helm/agent-monitor/values.yaml uses tag: "" and falls back to
the chart's appVersion. Leave it empty.client, mcp, monitoring, and vscode-extension ship on their own
versions and are asserted not to equal the root release.Use the repository resolved from the current checkout and the intended authenticated GitHub identity. Run gh auth status before any mutation and stop if the active account is not the account intended for the repository:
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"
)"
existing is empty, create the milestone with gh api --method POST "repos/${repo}/milestones" -f title="${milestone}".PATCH /repos/{owner}/{repo}/issues/{number} with the numeric milestone returned by the completed milestone step.gh pr view "$pr" --json closingIssuesReferences. Assign each same-repository issue through the same numeric-milestone REST field.gh pr view "$pr" --json milestone,closingIssuesReferences, then query each linked issue's milestone.extensions:sync.closingIssuesReferences is available, or leave linked release work assigned to a different version.npm run release:bump -- <component> only for a controlled local fallback.references/version-checklist.mdChoose 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/p
---name: version-releasedescription: Choose and apply the correct semantic version bump for this repository. Use for every user-visible release…---# .claude/skills/version-release/SKILL.mdVisão geral
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.
Perguntas frequentes
Baixe .claude/skills/version-release/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/hoangsonww/Claude-Code-Agent-Monitor.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.
npm run extensions:validate, relevant tests/builds, and ccam version or node bin/ccam.js version.client, mcp, monitoring, or VS Code extension packages unless those products are also being released.