skills.rest
chiragborse1
chiragborse1COMMUNITY
Explore all skills by this author →
Website𝕏@chiragborse1GitHub

openclaw-release-maintainer

Manage and validate Kova and Openclaw release and publishing workflows.

Updated Aug 23, 2026
Search Tags:#changelog#npm#macos#release-management#github-actions#preflight#artifact-verification
One-click install
npx skills add https://github.com/chiragborse1/Kove --skill openclaw-release-maintainer-chiragborse1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-release-maintainer
Source: https://github.com/chiragborse1/Kove/tree/main/.agents/skills/openclaw-release-maintainer
Command: npx skills add https://github.com/chiragborse1/Kove --skill openclaw-release-maintainer-chiragborse1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a guarded, repeatable maintainer workflow to prepare, validate, and publish Kova/Openclaw releases while preventing accidental version drift, improper publishes, and incomplete artifact verification.

Core Features & Use Cases

  • Release guardrails: Enforces permission checks, explicit operator approval, and rules for stable, beta, and dev channel naming.
  • Version synchronization: Ensures versions match across package.json, platform plist/gradle files, and docs before tagging.
  • Preflight and validation: Describes required preflight checks for npm and macOS, saving preflight run IDs, and verifying published artifacts and appcast updates.
  • Coordinated publish flow: Guides the multi-repo workflow_dispatch sequence, private mac preflight/publish lanes, and artifact promotion to GitHub releases.
  • Use Case: Prepare a beta or stable release, run all preflight validations across npm and macOS lanes, assemble changelog-backed release notes, and perform the publish step with saved preflight IDs.

Quick Start

Prepare and validate a Kova release for the target version by running the full preflight checks, assembling release notes from CHANGELOG.md, verifying artifacts, and only then creating the git tag and dispatching the publish workflows.

Frequently Asked Questions about openclaw-release-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent version drift when preparing a release across npm and macOS?▼

Preflight validation for npm and macOS requires running specific checks, saving preflight run IDs, and verifying published artifacts. You must save these preflight run IDs to reference them during the coordinated publish step and verify that artifacts and appcast updates are correctly promoted.

What is the correct workflow_dispatch sequence for a coordinated multi-repo publish?▼

The correct workflow_dispatch sequence involves guided multi-repo dispatching, private mac preflight and publish lanes, and artifact promotion to GitHub releases. It requires explicit guarded workflow_dispatch approvals and adherence to appcast and release naming rules across both public and private repositories.

Does GitHub Actions support guarded approvals for beta and stable channel releases?▼

Yes, guarded approvals for beta and stable channel releases are supported through explicit operator approval and permission checks. The workflow enforces rules for stable, beta, and dev channel naming alongside guarded workflow_dispatch approvals before any publishing actions execute.

How do I assemble changelog-backed release notes for a GitHub Actions publish?▼

Assembling changelog-backed release notes involves extracting entries from CHANGELOG.md to prepare release notes for the target version. This happens after preflight validations pass and before you create the git tag and dispatch the coordinated publish workflows.

Why does artifact verification fail when publishing across public and private GitHub workflows?▼

Artifact verification fails when preflight run IDs are not saved or when published npm and macOS assets do not match expected appcast updates. The workflow requires saving preflight run IDs and verifying artifacts against appcast and release naming rules before promotion to GitHub releases.

Related Skills

Explore More Software Engineering Skills→
juanmicrosoftjuanmicrosoft
3

create-release

Automate Calor release processes with version management, benchmarks, pull requests, and GitHub tagging.

Community
Advanced
borealBytesborealBytes
7

release-openclaw-mac

Automate signing, notarization, appcast promotion, and asset publishing for OpenClaw macOS releases.

Community
Advanced
rickylabsrickylabs

netscript-release

Automate NetScript release cuts and GitHub publishing with Deno and GitHub Actions.

Community
Advanced
majunbaomajunbao

openclaw-release-maintainer

Coordinate OpenClaw release workflows across changelogs, npm, and macOS packaging.

Community
Advanced