/ops-restore

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select ops-restore from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv ops-restore, /just-vibe ops-restore and /jv:ops-restore in Claude. See shortcut setup and context examples.

What the agent does

1. Verify backup identity, provenance, completeness and keys, and plan destination isolation.
2. Restore into the isolated destination in apply mode.
3. Reconcile schema, counts, integrity and application behavior, and record recovery duration and the data-loss window.

Inputs

• backup identity, source system, isolated destination, recovery objectives, and encryption/access prerequisites.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Validate restoration and readiness; production replacement requires exact explicit authorization.

Writes

Inspect/plan: plan the restore; save requested artifacts only. Apply: restore only into the named isolated destination and run integrity and application checks against it; never overwrite the source system or a shared database. Production replacement requires its exact explicit authorization.

Mode

Plan; backup identity, source system, isolated destination, recovery objectives, and encryption/access prerequisites. A requested rehearsal uses apply mode and writes only to the named isolated destination.

Prerequisites

Exact service/environment, time window, revision/configuration identity, authorized logs/metrics, and operational constraints. Prefer observation before intervention; live restarts, traffic changes, restores, and notifications require the requested target/action. Redact sensitive telemetry.

Expected output

• Restore procedure or exercise report with source/target identities, recovery timing and data-loss window, integrity and application results, and limitations.

How the work is checked

• Restore succeeds into the intended isolated destination; a readable backup alone does not count as demonstrated recoverability.

When to stop or clarify

• Never overwrite live data implicitly. Missing keys, integrity checks, or target identity stops execution before destructive steps.

Handling missing context

Infer

Read service/environment, time window, revision, available telemetry and existing incident or recovery procedure.

Assume

Start from supplied logs and read-only observation; rank hypotheses without presenting an unexecuted intervention as recovery.

Ask

Resolve the precise target and missing authority before restart, restore, notification or traffic changes; continue evidence analysis while waiting.

Technical guidance

Evidence

Resolve backup identity, encryption access, retention, destination isolation and recovery objectives.

Method

Restore into a verified separate target and validate schema, membership, constraints and application behavior.

Pitfall

A readable archive or backup job success does not prove restoration; testing on production can overwrite current data.

Check

Measure restored data cutoff and elapsed recovery, verify integrity and application checks, and retain the failed-step recovery plan.

Situational decisions

When backup reads successfully but application checks fail: Treat recovery as incomplete and preserve the isolated target for diagnosis; do not overwrite the live source.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring