upgrade-guard

Orchestrate OpenClaw gateway upgrades with snapshots, pre-flight checks, and rollbacks.

9|2|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/jzOcb/upgrade-guard --skill upgrade-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-guard
Source: https://github.com/jzOcb/upgrade-guard/tree/main
Command: npx skills add https://github.com/jzOcb/upgrade-guard --skill upgrade-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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.

Frequently Asked Questions about upgrade-guard

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

FAQPage Schema
How do I prevent OpenClaw upgrades from breaking plugins and configs?

You can prevent OpenClaw upgrade breakages by orchestrating system snapshots, running pre-flight validation, and executing controlled installs with automatic rollback if gateway health verification fails.

What is the safest way to rollback a failed OpenClaw gateway update?

The safest rollback method restores a pre-upgrade snapshot, reverting the git state, plugin inventory, symlinks, and channel list to their previous working versions when post-verification checks fail.

Does OpenClaw upgrade automation work with pnpm and systemd?

Yes, OpenClaw upgrade automation integrates with pnpm for dependency installation and systemd-friendly watchdog timers to monitor gateway processes, HTTP endpoints, and trigger emergency rollbacks.

How do pre-flight checks validate an OpenClaw version bump?

Pre-flight checks validate an OpenClaw version bump by verifying snapshot existence, config validity, git cleanliness, disk space sufficiency, and analyzing remote commits for breaking changes before initiating the upgrade.

Why does my OpenClaw gateway become unreachable after a git pull?

An OpenClaw gateway becomes unreachable after a git pull when new code introduces broken dependencies or invalid configs, which is why controlled upgrade flows stop the gateway, pull code, and verify health before completing.

Can I monitor OpenClaw system resources and automatically restart the gateway?

Yes, you can monitor OpenClaw system resources and automatically restart the gateway using a systemd or cron watchdog timer that checks HTTP endpoints, Telegram, and system resources, rolling back when thresholds are exceeded.