openclaw-release-maintainer
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.
Best for OpenClaw project maintainersWorks with GitHubHigh risk
⌘source
- author
@openclaw- language
- TypeScript
★360kstars
73kforks
Apr 17, 2026
✦overview.md
Key Features
- ·Maintains OpenClaw stable and beta releases
- ·Aligns version naming conventions
- ·Assembles release notes and changelogs
- ·Validates publish-time commands and artifacts
- ·Checks release authorization requirements
- ·Follows documented release guardrails
Use Cases
- →Preparing a stable release of OpenClaw for npm publication
- →Creating and publishing a beta prerelease version
- →Verifying release artifacts and commands before publishing
- →Assembling changelog release notes for a new version
- →Aligning version naming across Git tags and npm packages
Best for
- ✓OpenClaw project maintainers
- ✓Release engineering workflows
- ✓CI/CD pipeline validation
Not ideal for
- !Ordinary development changes
- !GHSA-specific advisory work
- !One-off scripting or automation
FAQs
name
openclaw-release-maintainer
description
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.
OpenClaw Release Maintainer
Use this skill for release and publish-time workflow. Keep ordinary development changes and GHSA-specific advisory work outside this skill.
Respect release guardrails
- Do not change version numbers without explicit operator approval.
- Ask permission before any npm publish or release step.
- This skill should be sufficient to drive the normal release flow end-to-end.
- Use the private maintainer release docs for credentials, recovery steps, and mac signing/notary specifics, and use
docs/reference/RELEASING.mdfor public policy. - Core
openclawpublish is manualworkflow_dispatch; creating or pushing a tag does not publish by itself.
Keep release channel naming aligned
stable: tagged releases only, published to npmbetaby default; operators may target npmlatestexplicitly or promote laterbeta: prerelease tags likevYYYY.M.D-beta.N, with npm dist-tagbeta- Prefer
-beta.N; do not mint new-1or-2beta suffixes dev: moving head onmain- When using a beta Git tag, publish npm with the matching beta version suffix so the plain version is not consumed or blocked
$install
1-click copynpx skills add openclaw/openclaw --skill openclaw-release-maintainerSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.