openclaw-release-maintainer

Coordinate OpenClaw release workflows and validate npm and macOS publish steps.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/karaabd23-crypto/openclaw --skill openclaw-release-maintainer-karaabd23-crypto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-release-maintainer
Source: https://github.com/karaabd23-crypto/openclaw/tree/main/.agents/skills/openclaw-release-maintainer
Command: npx skills add https://github.com/karaabd23-crypto/openclaw --skill openclaw-release-maintainer-karaabd23-crypto

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

  • Release workflow orchestration for stable and prerelease branches, including changelog generation and release notes assembly.
  • Validation and preflight checks for npm, macOS, signing/notarization, and feed updates.
  • Guardrails and approvals to ensure operator authorization before performing release steps and to coordinate branch-based release work across teams.

Quick Start

Run the maintainer script to begin the release validation sequence.

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 release notes assembly for npm and macOS builds?

Automate changelog generation and release notes assembly by orchestrating release workflows across stable and prerelease branches, validating publish-time commands and artifacts to ensure npm and macOS builds meet governance requirements.

What validation checks are required for macOS signing and notarization during a release?

macOS signing and notarization validation requires passing preflight checks that verify credential handling and artifact integrity, ensuring release branches meet specific auth requirements before publish-time commands execute.

How do I coordinate stable and beta release branches without failing governance checks?

Coordinate stable and beta release branches by implementing guardrails and prerequisite checks that ensure operator authorization, align version naming, and validate credentials before proceeding with release steps.

Can I use this workflow to verify npm publish commands before executing a release?

Yes, you can verify npm publish commands through built-in preflight validation checks that confirm branch alignment, credential handling, and release auth requirements before executing the actual publish sequence.

Why do my release validation checks fail when switching between private workflows and npm?

Release validation checks fail when prerequisite guardrails detect missing operator authorization or misaligned version naming, preventing transitions between private workflows and npm until credential requirements are met.