openclaw-release-maintainer

Coordinate release, changelog, and publishing workflows for stable and beta builds.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw Release Maintainer automates and validates the end-to-end release workflow, including changelog generation, release notes, tagging, and artifact publication for stable and beta builds.

Core Features & Use Cases

  • Orchestrates branch management, changelog rewrites, and version tagging across npm and macOS release pipelines.
  • Coordinates preflight validation, test suites, and release asset packaging to ensure compliant, auditable releases.
  • Guides operators through guardrails, credential handling, and public documentation alignment during release cycles.

Quick Start

Trigger the release-maintainer workflow for the target tag and follow the prompts to provide credentials and release notes.

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 release workflows and changelog generation?

Automating npm release workflows and changelog generation involves orchestrating branch management, preflight validation, and version tagging. This Skill coordinates these pipelines to ensure compliant, auditable stable and beta builds.

What is the process for coordinating macOS and Sparkle release pipelines?

The process for coordinating macOS and Sparkle release pipelines requires guiding operators through asset packaging, tagging, and guardrails. Manual-credential prompts and documentation references ensure secure, compliant releases across main or release branches.

Can I use this workflow for both stable and beta build releases?

Yes, this workflow supports both stable and beta build releases. It applies branch management, preflight validation, and asset packaging across npm, macOS, and Sparkle pipelines for releases on main or release/YYYY.M.D branches.

How do I handle manual credentials during the tagging and publishing process?

Handling manual credentials during the tagging and publishing process involves following interactive prompts to provide necessary authentication. The workflow implements guardrails and documentation references to ensure secure credential handling and compliant releases.

Does preflight validation run automatically before npm and macOS asset packaging?

Yes, preflight validation runs as a coordinated step before npm and macOS asset packaging. The workflow orchestrates test suites and release asset packaging to ensure all builds are validated and compliant prior to tagging and publication.

Why does the release workflow require branch management on release/YYYY.M.D branches?

The release workflow requires branch management on release/YYYY.M.D branches to isolate changes, apply guardrails, and coordinate preflight validation. This ensures stable and beta builds are properly tagged and auditable across npm and macOS pipelines.