openclaw-release-validation

Validate OpenClaw main commits against a real gateway with isolated or in-place testing.

388k|81.5k|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/openclaw/openclaw --skill openclaw-release-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-release-validation
Source: https://github.com/openclaw/openclaw/tree/main/.agents/skills/openclaw-release-validation
Command: npx skills add https://github.com/openclaw/openclaw --skill openclaw-release-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Validating a new OpenClaw release against a live gateway is risky and time-consuming, requiring careful isolation, manual testing, and structured reporting. This Skill automates preparation, finding triage, and reporting while keeping the human in control of testing and quality judgment.

Core Features & Use Cases

  • Isolated OCM Copy Testing: Creates a disposable OCM-managed copy of a gateway to safely test the latest main commit without affecting production state.
  • In-Place Gateway Updates: Optionally updates a real gateway to the latest main build with explicit approval, backup, and dry-run verification.
  • Structured Campaign Reporting: Joins the existing release-validation campaign issue, triages findings, and publishes a consolidated report with a hidden JSON payload for dashboards.
  • Use Case: A release manager needs to validate the latest beta of OpenClaw before promoting it to stable. They invoke this Skill, choose an isolated OCM copy of their test gateway, run through the priority surfaces, and submit a single structured report to the campaign issue.

Quick Start

Use the openclaw-release-validation skill to test the latest main commit against my gateway and prepare a release feedback report.

Frequently Asked Questions about openclaw-release-validation

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

FAQPage Schema
How do I validate an OpenClaw release against my gateway safely?

Use an isolated OCM copy of your gateway to test the latest main commit without modifying production state. The skill creates a disposable environment, runs readiness checks, and guides you through manual surface testing before publishing findings.

What is the difference between isolated OCM copy and in-place gateway testing?

Isolated OCM copy creates a disposable clone that fails closed if containment cannot be proven. In-place mode modifies your real gateway after explicit approval, creates a verified backup, and may migrate state and plugins.

Does the release validation skill require OCM to be installed?

OCM is required for the isolated-copy option and will be installed on request. For in-place updates on a plain personal gateway, OCM is not required and the openclaw CLI is used directly.

Why does the skill refuse to update when OCM isolation fails?

Containment is treated as a hard gate to protect against unresolved source-state escapes. If OCM cannot prove candidate-writable paths stay inside the environment, the skill pauses and offers the mode choice again.

Can I submit release feedback without testing all priority surfaces?

Yes. Any scorecard surface may be tested, and the worksheet records only the surfaces you actually exercised. The final report reflects your tested surfaces and authored findings.