upgrade-guard

What problem does it solve?

OpenClaw upgrades often break plugins, dependencies, configs, models, and channels in ways that leave your gateway unusable and your AI agent unreachable, so this skill orchestrates safe transitions that protect every layer of your stack.

Core Features & Use Cases

• Snapshot orchestration: capture the current version, git state, config, plugin inventory, symlinks, channel list, and gateway health before making any changes.
• Pre-flight checks: ensure snapshots exist, configs are valid, git is clean, disk space is sufficient, and remote commits are analyzed for breaking changes before upgrading.
• Controlled upgrade flow: stop the gateway, pull the latest code, install dependencies, build, restart services, verify health, and automatically rollback if verification or the gateway fails.
• Post-verification & rollback: confirm plugins, configs, models, symlinks, logs, and gateway health after upgrades and restore everything from the snapshot when emergencies strike.
• Watchdog monitoring: keep a systemd/cron timer checking gateway processes, HTTP, Telegram, and system resources, restarting or rolling back via upgrade-guard when thresholds are exceeded.
• Use case: before a risky version bump, snapshot the running system, check for breaking commits, upgrade with the skill, and let the watchdog heal the gateway if the upgrade destabilizes it.

Quick Start

Ask upgrade-guard to snapshot your current OpenClaw state, run pre-flight checks, and perform the controlled upgrade with verification plus rollback readiness.