What problem does it solve? Cutting an OpenClaw release involves many coordinated steps—version alignment across multiple files, changelog-backed release notes, preflight validation, npm trusted publishing, and macOS signing/notarization—and missing any one of them can ship a broken or inconsistent release. This Skill encodes the full maintainer workflow so releases follow the correct sequence every time. ## Core Features & Use Cases - Release Channel Management: Enforces naming rules for stable, beta, and dev channels, including npm dist-tags and beta version suffixes like -beta.N. - Version & Changelog Alignment: Ensures every version location (package.json, iOS/macOS plists, Android gradle, docs) matches the release tag, and builds user-facing release notes from CHANGELOG.md. - Publish-Time Validation: Runs release checks, install smoke tests, and post-publish verification against the npm registry before and after publishing. - Use Case: When preparing OpenClaw v2025.1.2-beta.1, use this Skill to align all version files, run preflight workflows (npm, public mac validation, private mac preflight), create the tag and prerelease, then dispatch the real publish runs and verify the uploaded zip, dmg, and dSYM assets. ## Quick Start Ask the agent to prepare and validate the OpenClaw release for a specific version tag, running all preflight checks before any publish step.
