释放创建
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 文档
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 运行环境要求
- Node.js
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
Use this skill after the release code version has already been committed to the repository. Keep code-version bumping separate.
This skill creates a release by:
1. Verifying the requested version matches both `apps/node/package.json` and `apps/node/package-lock.json`.
2. Refusing to proceed unless `CHANGELOG.md` already contains exactly one release block for the requested version.
3. Refusing to proceed if the version is already published on npm, if the tag already exists, or if a GitHub Release already exists.
4. Running the same local Node checks used by `.github/workflows/publish-npm.yml`:
- `npm --prefix apps/node ci`
- `npm --prefix apps/node run build`
- `npm --prefix apps/node run test`
5. Creating an annotated `v<version>` tag at the requested SHA.
6. Pushing only that tag.
7. Inspecting the resulting `Publish npm Package` and `Release APK` workflow runs with `gh`.
8. Attempting `.agents/skills/release-update-published-version/` after the workflows succeed, retrying briefly for npm/GitHub propagation and creating a follow-up local commit for public docs and website content when the release is discoverable.
Run:
```bash
cd "$(git rev-parse --show-toplevel)"
.agents/skills/release-create/scripts/create_release.sh <version> [sha]
```
Example:
```bash
.agents/skills/release-create/scripts/create_release.sh 0.9.6
```
If `sha` is omitted, the script tags `HEAD`.
## Preconditions
- The target release commit must already exist locally.
- `apps/node/package.json` and `apps/node/package-lock.json` must already contain the target version.
- `CHANGELOG.md` must already contain exactly one `## [<version>]` block for the target release.
- Public release-facing docs do not need to be pre-bumped. This skill will try to prepare the published-version follow-up after the release succeeds.
- `git`, `npm`, and `gh` must be installed and authenticated.
## Safety Rules
- Do not force-move existing tags.
- Do not publish a version that already exists on npm.
- Do not push a branch as part of this step. Push the tag only.
- Do not use this skill to repair a partially published version. Bump to a new version instead.
- The post-release published-version update is a separate local commit. Review and push or merge it explicitly.
- If npm or GitHub Release propagation is still catching up after the workflows finish, the script reports a skipped published-version update instead of failing the release. Run `.agents/skills/release-update-published-version/` later in that case.
## Output Expectations
The script prints:
- release version
- target tag
- target commit SHA
- local validation status
- pushed tag confirmation
- detected workflow run URLs and conclusions
- published-version follow-up commit information when the release is already discoverable
- or a clear skipped message if publication metadata is still propagating
If a workflow does not appear quickly, the script reports that clearly instead of guessing success.
---
> Source: [clawperator/clawperator](https://github.com/clawperator/clawperator) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
前提条件
安全规则
产出预期
文件/命令 -> apps/node/package.json · apps/node/package-lock.json · CHANGELOG.md · .github/workflows/publish-npm.yml · npm --prefix apps/node ci · npm --prefix apps/node run build · npm --prefix apps/node run test · v<version>
内容校验值 -> 18a7bd78e38e
当前原文的自动摘译,尚未人工审校。
前提条件
目标发布提交必须已存在于本地。
apps/node/package.json和apps/node/package-lock.json必须已包含目标版本。对于目标版本,CHANGELOG.md必须已经恰好包含一个## [<version>]块。面向公开发布的文档不需要预先发布。该技能会在发布成功后尝试为发布版本后续做准备。必须安装并验证git、npm和gh。安全规则
不要强行移动现有标签。不要发布 npm 上已存在的版本。请勿在此步骤中推送分支。仅推送标签。不要使用此技能来修复部分发布的版本。改用新版本。发布后的发布版本更新是单独的本地提交。明确地查看并推送或合并它。
产出预期
该脚本打印:release version target tag target commit SHA 本地验证状态