What problem does it solve?
It prevents OpenClaw release and publish steps from drifting out of sync across npm, mobile/desktop version files, Sparkle feeds, tags, changelog-driven release notes, and CI validation by enforcing a single operational runbook for maintainers.
Core Features & Use Cases
- Release guardrails & approvals: Enforces version-change and publish permissions, requires operator intent, and separates normal development from GHSA advisory work.
- Channel-accurate naming and publishing: Aligns stable/beta/dev tagging conventions with npm dist-tags and version suffix rules so packages do not get consumed or blocked.
- Version, artifact, and Sparkle consistency: Ensures all listed version locations match tag-encoded versions, validates production vs beta appcast behavior, and supports correction-tag build-floor rules.
- Changelog-backed release notes: Generates GitHub release notes from the matching CHANGELOG version section with user-facing content ordering.
- Preflight and postpublish verification: Runs build/test/release checks, performs smoke validation, and verifies npm installation and upgrade paths after publishing.
Quick Start
Use this skill when you are preparing a stable or beta OpenClaw release and need Codex to run the full release preflight-to-publish sequence while keeping version files, appcast updates, and artifacts consistent with the tag and npm dist-tag.
