openclaw-release-maintainer

Automate and validate OpenClaw release workflows for versioning, changelogs, and publishing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The OpenClaw release maintainer process is complex and error-prone; this skill provides a structured workflow to prepare, validate, and publish releases, prereleases, and release notes to ensure consistency and reduce manual steps.

Core Features & Use Cases

  • Guardrails and checklists for versioning, changelog assembly, and publish validation
  • End-to-end release sequencing from tag creation to GitHub release publication
  • Use Case: prepare stable releases, beta prereleases, and associated artifacts with validated workflows

Quick Start

Initiate a release workflow by selecting a target version and validating all preflight checks before publishing.

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 release validation for GitHub tags and macOS packaging?

Release validation for GitHub tags and macOS packaging is automated by enforcing preflight checks, artifact validation, and version naming guardrails. This ensures correct publish-time steps and consistent release sequencing from tag creation to publication.

What is the best way to assemble changelogs and enforce version naming for a project release?

Assembling changelogs and enforcing version naming is handled through structured release workflows with built-in guardrails. These checklists validate versioning conventions and release notes before stable or prerelease tags are published to GitHub.

Can I use this workflow to prepare both stable releases and beta prereleases?

Yes, you can prepare both stable releases and beta prereleases. The workflow supports selecting a target version, validating preflight checks, and applying release policy guardrails to ensure correct tag creation and artifact publication.

How do I verify credentials and artifacts before publishing a GitHub release?

Credentials and artifacts are verified through automated preflight checks within the release workflow. This process validates publish-time steps, enforces version naming, and orchestrates artifact validation according to the project's release policy before publication.

Why does my release publish workflow fail versioning or changelog validation?

Release publish workflows fail validation when version naming conventions or changelog assembly do not meet the project's release policy guardrails. The workflow enforces these checks during preflight validation to prevent inconsistent or erroneous publish steps.