openclaw-release-maintainer

Coordinate OpenClaw release management across npm, GitHub, and Sparkle feeds.

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

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

  • Orchestrates release branches, version alignment, changelog assembly, and release-note validation across npm, GitHub releases, and macOS Sparkle feeds.
  • Validates credentials, access controls, and chain-of-trust for release artifacts; ensures guardrails against unsafe publishes.
  • Supports stable and beta release trains, prerelease validation, and post-release checks for reproducible deployments.

Quick Start

Prepare and validate an OpenClaw release by updating version tags, compiling changelog notes, and verifying publish-time credentials and artifacts.

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 version alignment for software releases?

Automate changelog generation and version alignment by coordinating release branches, compiling release notes, and validating publish-time commands. This workflow enforces guardrails for branch strategies and artifact integrity to ensure reproducible deployments across npm, GitHub, and macOS Sparkle feeds.

What is the best way to validate publish-time credentials and artifact integrity before a release?

Validate publish-time credentials and artifact integrity by enforcing guardrails that check release auth requirements, access controls, and chain-of-trust. This process prevents incorrect or unsafe publishes by verifying credentials and artifacts across npm, GitHub releases, and macOS Sparkle feeds.

Can I use this release workflow for both stable and beta version trains?

Yes, you can use this release workflow for both stable and beta version trains. It supports prerelease validation, version naming alignment, and post-release checks to ensure reproducible deployments across different release stages and platforms.

How do I prepare macOS Sparkle feeds and GitHub releases with proper guardrails?

Prepare macOS Sparkle feeds and GitHub releases by assembling release notes, aligning version naming, and validating publish-time commands. The workflow applies guardrails for credential checks and branch strategies to prevent unsafe or incorrect artifact publishing.

Why do I need to enforce branch strategies and credential checks during release validation?

Enforce branch strategies and credential checks during release validation to prevent incorrect or unsafe releases. These guardrails ensure access controls, chain-of-trust validation, and artifact integrity are verified before publishing to npm, GitHub, or macOS Sparkle feeds.

Does this release validation process support post-release checks for reproducible deployments?

Yes, this release validation process supports post-release checks for reproducible deployments. It validates publish-time commands, verifies artifact integrity, and ensures chain-of-trust across stable and beta release trains to maintain deployment consistency.