openclaw-release-maintainer

Name: openclaw-release-maintainer
Availability: InStock
Author: bitan-del

Automate OpenClaw release and publish-validation workflows across npm, macOS, and distro artifacts.

4|2|Updated Mar 26, 2026

Search Tags:#automation #changelog #versioning #publishing #release #openclaw

Ready to run

npx skills add https://github.com/bitan-del/gods-eye --skill openclaw-release-maintainer-bitan-del

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclaw-release-maintainer
Source: https://github.com/bitan-del/gods-eye/tree/main/.agents/skills/openclaw-release-maintainer
Command: npx skills add https://github.com/bitan-del/gods-eye --skill openclaw-release-maintainer-bitan-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and enforces governance for OpenClaw release cycles, prereleases, changelog generation, and publish-time validation.

Core Features & Use Cases

Release governance and guardrails: enforce operator approvals, version naming consistency, and mandatory preflight checks.
Changelog assembly and publish validation: collate user-facing release notes and verify artifacts, credentials, and signing readiness.
End-to-end publication readiness: coordinate multi-channel releases across npm, macOS, and artifact distribution with traceable audit trails.

Quick Start

Initiate the OpenClaw release workflow with the target version tag to start the end-to-end release sequence.

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 assembly and version validation for multi-channel npm and macOS releases?▼

Automated release workflows collate user-facing changelogs, validate version tags, and verify publish readiness across npm, macOS, and distro artifacts. This ensures controlled, auditable software handoffs with mandatory preflight checks.

What is the best way to enforce release guardrails and operator approvals for stable and beta release cycles?▼

Release governance guardrails enforce operator approvals, version naming consistency, and mandatory preflight checks across stable and beta cycles. This coordinates end-to-end release sequencing with traceable audit trails for controlled publication.

How does preflight publish validation work for npm, macOS, and distribution artifacts?▼

Publish validation verifies artifacts, credentials, and signing readiness before multi-channel distribution. It applies preflight checks across npm, macOS, and distro artifacts to ensure version alignment and changelog correlation for release readiness.

Can I coordinate prerelease versioning and changelog generation without manual publish checks?▼

Yes, automated workflows coordinate prerelease versioning and changelog generation while enforcing mandatory preflight checks. The system validates version alignment, collates release notes, and verifies credentials to ensure auditable publication readiness.

Does this release workflow require specific credential handling for multi-channel artifact distribution?▼

Yes, the workflow validates credentials and signing readiness as part of preflight checks for multi-channel publication. It coordinates artifact distribution across npm and macOS while maintaining traceable audit trails for controlled software handoffs.

Why do I need end-to-end release sequencing for OpenClaw version alignment and changelog correlation?▼

End-to-end release sequencing enforces version alignment and changelog correlation through guardrails and preflight checks. Without it, multi-channel publication across npm and macOS risks unverified artifacts and unauditable software handoffs.