openclaw-release-maintainer

Coordinate OpenClaw release workflows across changelogs, npm, and macOS packaging.

Updated Dec 6, 2016
One-click install
npx skills add https://github.com/majunbao/learn --skill openclaw-release-maintainer-majunbao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-release-maintainer
Source: https://github.com/majunbao/learn/tree/main/openclaw_tags/openclaw-2026.4.24/.agents/skills/openclaw-release-maintainer
Command: npx skills add https://github.com/majunbao/learn --skill openclaw-release-maintainer-majunbao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare and verify OpenClaw releases by coordinating changelogs, release notes, publish commands, and artifact handling, reducing manual errors and ensuring compliance with guardrails.

Core Features & Use Cases

  • Enforces release guardrails, branch naming conventions (e.g., release/YYYY.M.D), and checklist-driven workflows across npm, macOS, and internal gates.
  • Automates changelog rewrites and user-facing release notes to align with stable and beta trains, while preserving policy requirements.
  • Coordinates preflight validations, multi-stage approvals, and postpublish verification across CI/CD lanes, QA suites, and artifact publishing.
  • Bridges private maintainer docs and public release assets, orchestrating npm/publish workflows, macOS signing/notarization, and appcast updates.
  • Supports end-to-end release orchestration from drafting to public release, including rollback considerations and safety checks.

Quick Start

Initiate the end-to-end OpenClaw release workflow for the next version following guardrails and preflight checks.

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 for npm publishing?

Automated changelog rewriting and release notes generation are enforced during the release workflow to align content with stable and beta trains. The process coordinates publish commands and artifact management to reduce manual errors and ensure compliance with guardrails.

What is the standard branch naming convention for coordinating release workflows?

The standard branch naming convention for release workflows uses the format release/YYYY.M.D. Enforcing this naming structure is a core guardrail that ensures version consistency and checklist-driven workflow compliance across npm, macOS, and internal gates.

How do I run preflight checks and postpublish verification for a macOS app release?

Preflight validations and postpublish verification for a macOS app release are coordinated across CI/CD lanes and QA suites. The workflow orchestrates macOS signing and notarization, appcast updates, and artifact publishing to ensure full publish readiness.

Can I use release orchestration to manage both beta trains and mainline patch releases?

Release orchestration supports mainline releases, beta trains, and patch releases. It codifies versioning standards and multi-channel publication steps, applying appropriate guardrails, preflight checks, and safety validations for each specific release type.

Does the release workflow handle rollback considerations after multi-stage approvals?

The release workflow supports end-to-end orchestration from drafting to public release, including rollback considerations and safety checks. It coordinates multi-stage approvals and postpublish verification to manage artifacts and ensure safe publication across channels.