openclaw-release-maintainer

Automate OpenClaw release preparation, validation, and publishing via pnpm and GitHub workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating release processes for OpenClaw is complex and error-prone. This skill consolidates release sequencing, version alignment, changelog generation, and publish validation into a repeatable workflow that reduces human error.

Core Features & Use Cases

  • End-to-end release sequencing: prepares tags, validates artifacts, and triggers npm and macos publishing workflows.
  • Version governance: ensures all version locations (package.json, App metadata, changelog) reflect the target tag.
  • Changelog assembly and policy compliance: references CHANGELOG sections and policy guidelines for public release notes.
  • Preflight validation: runs build and smoke tests across release surfaces before publishing.
  • GHSA advisory handling: supports secure advisory inspection and patch policy within the maintainer flow.

Quick Start

Run the maintainer workflow to prepare and validate a new OpenClaw release by executing the preflight, tag creation, 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 npm and macOS release validation end-to-end?

Release validation for npm and macOS is automated by coordinating preflight checks, tag creation, and publish steps via pnpm and GitHub workflows. The workflow sequences artifact builds, smoke tests, and multi-channel publishing to reduce manual errors.

What is the best way to align version numbers across package.json and macOS app metadata?

Version alignment across package.json and platform-specific files is enforced by applying the target tag version across all metadata locations. This governance ensures consistency before changelog generation and publishing are triggered.

Can I use pnpm workflows to generate changelogs and validate artifacts before publishing?

Yes, pnpm workflows can assemble changelogs by referencing CHANGELOG sections and policy guidelines for public release notes. Preflight validation runs build and smoke tests across release surfaces before triggering the publish step.

Does this release workflow support GHSA advisory inspection and patch policy enforcement?

GHSA advisory handling is supported within the maintainer flow to enable secure advisory inspection and patch policy enforcement. This integrates security checks directly into the release sequencing and validation process.

How to troubleshoot inconsistent version tags during multi-channel npm and macOS publishing?

Inconsistent version tags during multi-channel publishing are prevented by guardrails that validate version consistency across package.json, App metadata, and changelogs before tag creation. Preflight checks halt the workflow if alignment fails.