agentleFS
Sign inStart free
hkyutonghkyutong/OneClaw/.agents/skills/openclaw-release-maintainer/SKILL.md

openclaw-release-maintainer

Skill1 starsChanged 8 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 7 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for release and publish-time workflow.

    line 8
  2. Distinctive:

    Do not change version numbers without explicit operator approval.

    line 12
  3. Distinctive:

    Ask permission before any npm publish or release step.

    line 13
  4. Very specific:

    Use the private maintainer release docs for the actual runbook and docs/reference/RELEASING.md for public policy.

    line 14
  5. Very specific:

    Prefer -beta.N; do not mint new -1 or -2 beta suffixes

    line 20
  6. Distinctive:

    When using a beta Git tag, publish npm with the matching beta version suffix so the plain version is not consumed or blocked

    line 22
  7. Distinctive:

    When cutting a mac release with a beta GitHub prerelease:

    line 40
  8. Very specific:

    create a prerelease titled openclaw YYYY.M.D-beta.N

    line 42
  9. Very specific:

    use release notes from the matching CHANGELOG.md version section

    line 43
  10. Very specific:

    Keep the top version entries in CHANGELOG.md sorted by impact:

    line 45
  11. Distinctive:

    Before tagging or publishing, run:

    line 51
  12. Very specific:

    Do not use NPM_TOKEN or the plugin OTP flow for core releases.

    line 68
  13. Distinctive:

    Only publish plugins that already exist on npm.

    line 70
  14. Very specific:

    Use openclaw-ghsa-maintainer for GHSA advisory inspection, patch/publish flow, private-fork validation, and GHSA API-specific publish …

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.
  • Use the private maintainer release docs for the actual runbook and docs/reference/RELEASING.md for public policy.

Keep release channel naming aligned

  • stable: tagged releases only, with npm dist-tag latest
  • beta: prerelease tags like vYYYY.M.D-beta.N, with npm dist-tag beta
  • Prefer -beta.N; do not mint new -1 or -2 beta suffixes
  • dev: moving head on main
  • When using a beta Git tag, publish npm with the matching beta version suffix so the plain version is not consumed or blocked

Handle versions and release files consistently

  • Version locations include:
    • package.json
    • apps/android/app/build.gradle.kts
    • apps/ios/Sources/Info.plist
    • apps/ios/Tests/Info.plist
    • apps/macos/Sources/OpenClaw/Resources/Info.plist
    • docs/install/updating.md
    • Peekaboo Xcode project and plist version fields
  • “Bump version everywhere” means all version locations above except appcast.xml.
  • Release signing and notary credentials live outside the repo in the private maintainer docs.

Build changelog-backed release notes

  • Changelog entries should be user-facing, not internal release-process notes.
  • When cutting a mac release with a beta GitHub prerelease:
    • tag vYYYY.M.D-beta.N from the release commit
    • create a prerelease titled openclaw YYYY.M.D-beta.N
    • use release notes from the matching CHANGELOG.md version section
    • attach at least the zip and dSYM zip, plus dmg if available
  • Keep the top version entries in CHANGELOG.md sorted by impact:
    • ### Changes first
    • ### Fixes deduped with user-facing fixes first

Run publish-time validation

Before tagging or publishing, run:

node --import tsx scripts/release-check.ts
pnpm release:check
pnpm test:install:smoke

For a non-root smoke path:

OPENCLAW_INSTALL_SMOKE_SKIP_NONROOT=1 pnpm test:install:smoke

Use the right auth flow

  • Core openclaw publish uses GitHub trusted publishing.
  • Do not use NPM_TOKEN or the plugin OTP flow for core releases.
  • @openclaw/* plugin publishes use a separate maintainer-only flow.
  • Only publish plugins that already exist on npm; bundled disk-tree-only plugins stay unpublished.

GHSA advisory work

  • Use openclaw-ghsa-maintainer for GHSA advisory inspection, patch/publish flow, private-fork validation, and GHSA API-specific publish checks.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free