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.