- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add arcee-ai/nac --skill release -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add arcee-ai/nac --skill release -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add arcee-ai/nac --skill release -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add arcee-ai/nac --skill release -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/arcee-ai/nac/tree/HEAD/.agents/skills/release來自發布者
Publish a stable NAC release end to end. A request for X.Y.Z or vX.Y.Z means complete the version bump, merge, annotated tag, GitHub Release, release automation, asset verification, and clean-install smoke test. Do not stop after preparing a branch or pull request.
This workflow is only for stable releases. Never create, edit, rerun, promote, or delete vX.Y.Z-rc.N tags or prereleases; the scheduled release workflow owns release candidates.
X.Y.Z and vX.Y.Z to VERSION=X.Y.Z and TAG=vX.Y.Z. Require canonical stable SemVer with exactly three numeric components and no prerelease or build suffix..github/workflows/release.yml, crates/nac-server/Cargo.toml, Cargo.lock, release-related scripts, and the latest stable GitHub Release before changing anything.origin/main.origin/main SHA. Find the Release workflow run for that SHA and wait until its required jobs succeed. An older green run does not authorize a newer commit.Record the initial main SHA, its successful workflow URL, the previous stable tag, and the target version. These values anchor the rest of the release.
Use only changes reachable from the commit that will be tagged.
The stable binary version is the nac-server package version. The release-managed files are:
crates/nac-server/Cargo.tomlnac-server package entry in Cargo.lockCompare the checked-in nac-server version with VERSION before opening a PR or creating public state. Stop if the checked-in version is greater than VERSION; never tag a higher-version binary with an older release tag.
If origin/main is below VERSION:
chore/release-vX.Y.Z from the captured main SHA.VERSION. Do not update dependencies or reformat unrelated files.cargo metadata --locked --no-deps --format-version 1 reports nac-server VERSION and all changed version-bearing entries agree.git diff --check and the repository's cheapest focused validation. Do not duplicate the full CI suite locally when required CI is available.chore(release): cut vX.Y.Z, push the branch, and open a ready-for-review PR to main with the same title.The PR body must state:
Wait for every required PR check. Merge with the repository's normal merge style only after all required checks pass. Then wait for the Release push workflow on the merge commit to succeed. Record the PR URL, merge SHA, and workflow URL.
If origin/main already contains exactly VERSION, identify the merged PR that introduced that version and verify its required checks and the current main workflow. Do not manufacture a no-op commit, edit an unrelated file, or open an empty release PR. Use the current green main SHA as the release commit and report why a second PR was unnecessary.
If main advances before tagging, do not silently include unreviewed commits. Recompute the change set and wait for CI on the intended release SHA, or stop if the release boundary is no longer clear.
Immediately before tagging, prove again that TAG is absent locally, on the remote, and in GitHub Releases.
Create an annotated tag on the exact verified release commit:
git tag -a "$TAG" "$RELEASE_SHA" -m "$TAG"
git push origin "$TAG"
Verify that the pushed object is an annotated tag and that peeling it resolves to RELEASE_SHA. Never move, replace, delete, or force-push a published stable tag.
Pushing the tag alone does not publish NAC assets. The stable asset workflow begins when the GitHub Release is published.
Write notes for users, not maintainers implementing the code:
## Bug fixes as the final section and summarize observable fixes there.TAG, at the end of that final section.Publish a stable, non-draft, non-prerelease GitHub Release for the existing tag. Its title must be exactly TAG:
Save the final notes to a local file and set NOTES_FILE to that path.
gh release create "$TAG" --verify-tag --title "$TAG" --notes-file "$NOTES_FILE" --latest
Release publication triggers .github/workflows/release.yml. Do not manually upload substitute artifacts while that workflow is running.
Release workflow run whose event is release, head branch is TAG, and head SHA is RELEASE_SHA.Verify from GitHub, not only from the local checkout:
TAG.RELEASE_SHA.nac-aarch64-apple-darwin.tar.gznac-x86_64-unknown-linux-musl.tar.gzINSTALL_DIR to a child directory before running scripts/install.sh against the published latest stable release. Invoke that exact installed path with -V and --version; require nac-web VERSION and the short form of RELEASE_SHA. Never overwrite or resolve through an existing user installation.Stop without mutating published state when:
Once a stable tag or Release is public, never delete, recreate, move, or overwrite it without explicit maintainer instruction. Finish all safe verification and report the exact blocker and public state.
Report concrete evidence:
push workflow URL and conclusion;release-event workflow URL and conclusion;-V and --version output;Prefer native repository and GitHub tools when the harness provides them. With GitHub CLI, use structured JSON from gh repo view, gh run list/view/watch, gh pr view/checks/merge, and gh release list/view/create/edit/download; avoid human-formatted tables when release identity, bodies, checks, or asset metadata could be truncated.
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidate
---name: releasedescription: Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a…---# .agents/skills/release/SKILL.md總覽
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
常見問題
從發布者下載 .agents/skills/release/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/arcee-ai/nac。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。