- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-release -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/HEAD/.agents/skills/version-releaseपब्लिशर से
Apply Semantic Versioning across CCAM:
X.Y.Z+1): backward-compatible fixes, docs-only work, dependency/security maintenance, refactors, or small improvements without a substantial new capability.X.Y+1.0): backward-compatible features or meaningfully larger capabilities such as new workflows, pages, integrations, API fields/routes, or major UX surfaces.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.
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. 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.
openapi.yaml.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).DEPLOYMENT.md, docs/DEPLOYMENT.md, and CITATION.cff.UI build v<version>, so regenerate and confirm the diff is only that line.npm run extensions:sync to regenerate Claude/Codex plugin manifests and both marketplaces.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.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.npm run extensions:validate, relevant tests/builds, and the CLI version check.server/__tests__/release-version-consistency.test.js is the machine-checkable release contract. Read it before bumping and run it after:
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":
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.
Do not hand-edit version surfaces when the automated workflow is available. Use npm run release:bump -- <component> only for a controlled local fallback.
Run gh auth status first. Stop if the active account is not the intended identity 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: create 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, then assign each same-repository issue through the same numeric-milestone REST field.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/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…---# .agents/skills/version-release/SKILL.mdओवरव्यू
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.
FAQ
पब्लिशर से .agents/skills/version-release/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/hoangsonww/Claude-Code-Agent-Monitor पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।