golem-rollback

Roll back Golem deployments to a previous revision or version label.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-rollback-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-rollback
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-rollback
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-rollback-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a Golem deployment goes wrong, you need a reliable way to restore the environment to a previously working state without rebuilding everything from scratch.

Core Features & Use Cases

  • Rollback by revision or version: Revert the environment to an exact captured revision number or to a revision selected by a version label.
  • Safe impact inspection: Preview the changes with a plan/dry-run style diff before applying the rollback.
  • Optional post-rollback agent handling: Update existing agents, redeploy agents, or reset the environment to ensure runtime matches the rolled-back state.
  • Use Case: After deploying a bad release that changed components or HTTP API behavior, rollback to the last known-good revision so the environment returns to the prior component versions and API configuration.

Quick Start

Run golem deploy --revision 3 --update-agents auto --yes to roll back the environment to revision 3 and automatically bring running agents to the rolled-back component versions.

Frequently Asked Questions about golem-rollback

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

FAQPage Schema
How do I rollback a Golem deployment to a previous revision?

You rollback a Golem deployment by specifying a target revision number or version label, which restores the environment to a previously captured state without triggering a new build.

What is the best way to recover from a bad Golem release without rebuilding?

Deployment rollback reverts component versions and HTTP API configurations to a known-good state atomically, avoiding a full rebuild. It performs a server-side switch to the target revision.

Can I preview changes before reverting an environment deployment?

Yes, you can preview changes before reverting. The rollback process computes and displays a diff against the current deployment, allowing you to inspect the impact before applying the state switch.

Does rollback automatically update running agents to the rolled-back version?

Rollback supports optional post-rollback agent handling. You can update existing agents, redeploy agents, or reset the environment to ensure the runtime matches the rolled-back component versions.

How do I skip confirmation prompts when reverting an API configuration?

You can skip confirmation prompts by including the --yes flag. This applies the atomic server-side switch to the target state immediately without requiring interactive confirmation.

When should I not use environment-level deployment recovery?

You should not use environment-level deployment recovery if the target revision does not exist. The rollback requires a valid previously captured state to compute the diff and revert safely.