How do I install the Release Create skill?

Run npx get-skill add tomevault-io/release-create in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release Create safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Create?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Create free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Create?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Create by tomevault-io — Agent Skill

Name: Release Create
Author: tomevault-io

Release Create

Validates a Clawperator release candidate, creates and pushes an annotated git tag for a specific version and commit, inspects the resulting GitHub Actions release workflows, and prepares the follow-up published-version docs update.

tomevault-io Updated Sep 17, 2026

File contents

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:

Verifying the requested version matches both apps/node/package.json and apps/node/package-lock.json.
Refusing to proceed unless CHANGELOG.md already contains exactly one release block for the requested version.
Refusing to proceed if the version is already published on npm, if the tag already exists, or if a GitHub Release already exists.
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
Creating an annotated v<version> tag at the requested SHA.
Pushing only that tag.
Inspecting the resulting Publish npm Package and Release APK workflow runs with gh.
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:

cd "$(git rev-parse --show-toplevel)"
.agents/skills/release-create/scripts/create_release.sh <version> [sha]

Example:

.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 — distributed by TomeVault.

---name: release-createdescription: Validates a Clawperator release candidate, creates and pushes an annotated git tag for a specific version and commit, inspects the resulting GitHub Actions release workflows, and prepares the follow-up published-version docs update.---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:```bashcd "$(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 ExpectationsThe 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 propagatingIf 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).

Frequently asked questions