菜单
Records release intent with Changesets and guides semver, changelog, CI, and artifact-version checks for independently distributed packages. Use when a repository has `@changesets/cli`, `.changeset/`, a version-packages PR, publishable plugins, SDKs, libraries, or monorepos.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Synthesize the current conversation and repository context into a concise product and engineering spec, publish it to the project issue tracker, and gate agent readiness before decomposition. Use when high-level work needs product framing, implementation and testing decisions, or success criteria captured without another general interview.
Add GitHub-visible AI agent and AI code-review metadata and exact agent labels without adding AI attribution to commits, and scope Alibaba/Open Code Review's review surface to control LLM token spend. Use when configuring PR templates, issue/PR labels, PR creation commands, PR update comments, or Alibaba Code Review/open code review workflows to disclose the implementing agent, review tool, LLM model, run URL, or to add/tune a `.opencodereview/rule.json`.
Define acceptance criteria, risk level, and verification before editing. Use at the start of non-trivial implementation or when an issue lacks clear proof of completion.
Check deployment, staging, rollback, and health verification before release. Use for user-facing, infrastructure, CI/CD, integration, or high-risk changes.
Clarify non-trivial engineering work before implementation by resolving ambiguity, terminology, constraints, and the smallest viable path. Use when a request is broad, fuzzy, architectural, cross-cutting, or has hidden product decisions.
Run an independent semantic review gate before merging non-trivial work, on top of (not duplicating) Alibaba Code Review and CI. Use after implementation and verification, especially for medium/high-risk changes.
| name | changesets-release |
| description | Records release intent with Changesets and guides semver, changelog, CI, and artifact-version checks for independently distributed packages. Use when a repository has `@changesets/cli`, `.changeset/`, a version-packages PR, publishable plugins, SDKs, libraries, or monorepos. |
Use this for consumer-installed packages. Do not require Changesets for a single deployed application unless its owner chooses release versions.
no-changeset convention. Do not add an empty changeset merely to satisfy CI..changeset/config.json, package metadata, and the consumer contract before choosing a bump.patch for compatible fixes, minor for compatible capabilities, and major for breaking behavior, removed APIs, or required consumer changes.changeset command and commit its generated .changeset/<name>.md with the implementation PR.no-changeset marker on releaseable PRs; changeset status is the non-interactive CI check.Changesets records release intent; it does not automatically update every native manifest. The version PR must update and verify every public version surface.
readme.txt stable tag, ZIP filename/metadata, Git tag, and release notes.release-gate for staging, rollout, rollback, and health checks.changeset status succeeds in CI for a releaseable change.