openclaw-release-maintainer

Automate OpenClaw release management with changelogs, release notes, and artifact publishing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates OpenClaw release preparation and verification, consolidating changelogs, release notes, and artifact publishing into a repeatable process.

Core Features & Use Cases

  • Automates changelog rewrites and release-note assembly for stable and beta releases.
  • Enforces release guardrails, branch naming, and preflight validation before publishing.
  • Integrates with private docs and artefact repositories to publish and track releases.

Quick Start

Initiate a release by creating a release/YYYY.M.D branch from main, rewrite the changelog, and kick off preflight and publishing 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 OpenClaw release workflows including changelogs and artifact publishing?

Automating OpenClaw release workflows involves streamlining changelog rewrites, release-note assembly, and artifact publishing into a single repeatable process. This Skill initiates the pipeline by creating a release branch from main, rewriting the changelog, and executing preflight validation before publishing.

What is the process for enforcing release guardrails and branch naming validation?

Enforcing release guardrails requires preflight validation checks across main and release branches. This Skill implements prerequisite checks and enforces specific branch naming conventions, such as creating a release/YYYY.M.D branch, to ensure version alignment and governance before publishing.

How do I manage beta and stable release trains for macOS packaging?

Managing beta and stable release trains for macOS packaging requires cross-platform alignment and branch strategies. This Skill automates release-note assembly for both beta and stable releases, ensuring version alignment and governance across different packaging scenarios.

Does the release workflow support integration with private artifact repositories?

Yes, the release workflow supports integration with private artifact repositories. This Skill connects with private repositories to publish and track releases, ensuring artifacts and accompanying documentation are distributed and maintained through a consolidated pipeline.

What are the limitations of manual release preparation compared to an automated workflow?

Manual release preparation lacks version alignment and governance across main and release branches. Automated workflows enforce prerequisite checks and preflight validation, reducing human error in changelog rewrites and artifact publishing, whereas manual processes cannot guarantee consistent cross-platform packaging governance.