skills.rest
wuv-dreamguide
wuv-dreamguideOFFICIAL
Explore all skills by this author →
GitHub

openclaw-release-maintainer

Automate OpenClaw release governance with changelog generation, version alignment, and publish validation.

Updated Apr 21, 2026
Search Tags:#automation#changelog#versioning#validation#release#macos
One-click install
npx skills add https://github.com/wuv-dreamguide/openclaw --skill openclaw-release-maintainer-wuv-dreamguide
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-release-maintainer
Source: https://github.com/wuv-dreamguide/openclaw/tree/main/.agents/skills/openclaw-release-maintainer
Command: npx skills add https://github.com/wuv-dreamguide/openclaw --skill openclaw-release-maintainer-wuv-dreamguide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

Core Features & Use Cases

  • End-to-end release governance for OpenClaw, including version alignment, changelog updates, and publish validation across npm and macOS pipelines.
  • Guardrails to ensure release hygiene, including branch discipline, sign/notarize steps, and controlled tag creation.
  • Use Case: Prepare a beta release on a release/YYYY.M.D branch and verify before publishing.

Quick Start

Run the release-maintainer workflow on the designated release branch to begin end-to-end release validation.

Frequently Asked Questions about openclaw-release-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate changelog generation and version alignment for releases?▼

You can prepare a beta release on a release/YYYY.M.D branch by running the release-maintainer workflow. It performs end-to-end validation, verifies version naming, and checks publish-time prerequisites before you publish artifacts.

Can I use release automation for macOS sign and notarize steps?▼

Yes, release automation applies to macOS pipelines by enforcing sign and notarize steps as prerequisites. It orchestrates artifact validation and references private docs for platform-specific credentials and publishing steps.

What is the best way to validate publish-time commands and artifacts?▼

The best way to validate publish-time commands is through controlled release governance. The workflow applies safeguards for artifact validation, release authentication, and branch discipline to ensure publish hygiene across npm and macOS pipelines.

Does release governance enforce branch discipline and tag creation?▼

Yes, release governance enforces branch discipline and controlled tag creation as core guardrails. These safeguards ensure release hygiene, align version naming, and prevent unauthorized publishes across beta and stable branches.

Why does preflight validation fail before publishing an OpenClaw release?▼

Preflight validation fails when release hygiene checks detect misaligned version naming, missing sign or notarize steps, or incorrect branch discipline. The workflow orchestrates these prerequisites to block invalid artifacts from publishing.

Related Skills

Explore More Software Engineering Skills→
191854169191854169

openclaw-release-maintainer

Automate and validate OpenClaw release workflows for versioning, changelogs, and publishing.

Community
Advanced
pwarnockpwarnock
2

release-publishing

Automate release planning and publishing workflows with Changesets and semantic versioning.

Community
Intermediate
dyoshikawadyoshikawa
1.3k

draft-release

Draft a GitHub release with changelog notes from ./tmp/release-notes/*.md.

Community
Intermediate
seasonmacseasonmac

openclaw-release-maintainer

Coordinate OpenClaw release management across npm, GitHub, and Sparkle feeds.

Community
Advanced