openclaw-release-maintainer

Automate OpenClaw release preparation and validation across npm, macOS, and changelog workflows.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/zyj18860969891-byte/openclaw-railway --skill openclaw-release-maintainer-zyj18860969891-byte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-release-maintainer
Source: https://github.com/zyj18860969891-byte/openclaw-railway/tree/main/.agents/skills/openclaw-release-maintainer
Command: npx skills add https://github.com/zyj18860969891-byte/openclaw-railway --skill openclaw-release-maintainer-zyj18860969891-byte

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

  • Automates release tagging and version alignment across npm, macOS, and changelog.
  • Generates and compiles user-facing release notes from CHANGELOG.md and PRs.
  • Validates publish-time prerequisites (credentials, signatures, notary, and artifact availability) before a release.

Quick Start

Run this skill to initiate a full release preflight, tag the release, and validate artifacts and publish steps.

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 release tagging and version alignment for npm and macOS publishing?

Automate release tagging and version alignment by coordinating version naming and changelog assembly across npm, macOS, and changelog workflows. The process applies preflight checks, tag creation, and artifact validation for stable and beta releases.

How can I validate publish-time prerequisites like credentials and signatures before a release?

Validate publish-time prerequisites by enforcing guardrails around credentials, signing, and release policy. The system checks credentials, signatures, notary, and artifact availability to prevent misconfigurations before operator approval.

What is the best way to compile user-facing release notes from a changelog and pull requests?

Compile user-facing release notes by generating and assembling them directly from existing CHANGELOG.md files and merged PRs. This ensures changelog release notes align with version naming during prerelease and stable release preparation.

Can I use this workflow to prepare both stable and beta releases?

Yes, the workflow prepares both stable and beta releases. It automates preflight checks, tag creation, and artifact validation across npm and macOS platforms while requiring operator approval before final publishing.

Why does publish validation require operator approval before releasing artifacts?

Publish validation requires operator approval to enforce guardrails around credentials, signing, and release policy. This prevents misconfigurations and ensures all publish-time prerequisites pass before any stable or beta release is executed.

When do I need to run release preflight checks for OpenClaw versioning?

Run release preflight checks when preparing stable or beta releases to align version naming, validate artifacts, and verify publish-time commands. This ensures all credentials, signatures, and notary requirements pass before tag creation.