Agent skill · steipete

openclaw-release-validation

Guide human release testing on an isolated OCM copy or approved in-place gateway, collect feedback, or refresh the release campaign.

What it needs

About 2k tokens when loaded.

What this skill does

OpenClaw Release Validation Help a human test an immutable latest-main build against a selected real Gateway's state. Automate preparation, triage, and reporting; the human drives interactive surfaces and judges quality. This skill collects feedback, not a release go/no-go decision. Choose the mode Campaign artifact: only when RELEASEVALIDATIONARTIFACTPATH is present. Read artifact generation, write that artifact, and stop. GitHub is read-only; no skill-update request or interactive setup. Update campaign: for an explicit refresh request, read installed skill check, then campaign lookup/dispatch. Dispatch the isolated runner for the selected explicit tag, verify its issue, and stop. Never analyze or edit the canonical issue yourself. Validate release: default human-testing workflow below. It joins the campaign; it never creates or rewrites the issue body directly. Human validation 1. Read installed skill check. Introduce the run briefly: choose a Gateway, protect it with a disposable OCM copy or approve an in-place update, prepare the pinned main build, then test and review feedback. 2. Read campaign lookup/dispatch. Require a current campaign and record its stable train and current beta. Gateway preparation pins the main test target separately. 3. Read Gateway preparation. Discover without mutation, let the tester choose source and mode, then prepare the selected target. Never use the caller's active checkout. 4. Only after readiness succeeds, offer local diagnostics for an isolated target, then read human testing to create the worksheet and guide one chosen surface at a time. 5. On finish validation, read cleanup and report approval. It handles blocked upgrades too. Review the complete batch before any post and preserve the exact structured-report contract. Before readiness is terminal, show only campaign/beta identity, source/mode choice, and upgrade progress or errors. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills steipete/openclaw-release-validation

View the source on GitHub

Browse the @skills marketplace