ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 2/5

emergency-rescue

Recover from developer disasters. Use when someone force-pushed to main, leaked credentials in git, ran out of disk space, killed the wrong process, corrupted a database, broke a deploy, locked themselves out of SSH, lost commits after a bad rebase, or hit any other "oh no" moment that needs immediate, calm, step-by-step recovery.

Why use this skill?

Recover from git disasters, lost commits, full disks, and system failures with the OpenClaw emergency-rescue skill. Calm, step-by-step recovery.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/gitgoodordietrying/emergency-rescue
Or

What This Skill Does

The emergency-rescue skill acts as a digital first-aid kit for software engineers facing critical, time-sensitive infrastructure or version control failures. It provides a structured, non-destructive, and calm environment to navigate technical crises. Rather than panicking when a repository is corrupted or a production environment enters an inconsistent state, the agent guides the user through a three-step protocol: diagnose, fix, and verify. The skill is designed to handle a wide range of 'oh no' moments, from accidental force-pushes to database migration failures, ensuring that even under high pressure, the user executes the most precise and safest recovery commands available. It serves as an expert technical consultant that prevents further damage by prioritizing recovery pathways that favor data safety over speed.

Installation

You can install this skill directly via the OpenClaw command-line interface or by using the installer within your dashboard:

clawhub install openclaw/skills/skills/gitgoodordietrying/emergency-rescue

Ensure you have the necessary permissions if the agent requires read/write access to your local git repositories or system process tables.

Use Cases

  • Git Recovery: Restoring lost history after accidental rebase operations, cleaning up commits pushed to the wrong branch, or undoing disastrous force-pushes on shared team repositories.
  • System Maintenance: Managing runaway processes that are pinning CPU or memory, and freeing disk space when system-critical services fail to boot due to storage limitations.
  • Credential Security: Identifying and remediating accidental commits containing sensitive tokens or API keys to prevent data breaches.
  • Deployment Hot-Fixes: Executing immediate rollbacks when automated CI/CD pipelines break in production.

Example Prompts

  • "OpenClaw, I just force-pushed to main by mistake. How do I restore the remote repository to the state it was in ten minutes ago?"
  • "My build is failing because the disk is full. Help me identify the largest files or processes that I can safely remove right now."
  • "I ran a git rebase and lost three days of work. Help me use the reflog to recover those commits before I make things worse."

Tips & Limitations

This skill is highly effective for recovery but should not be used as a replacement for daily backups or robust CI/CD testing protocols. Always run commands in 'dry-run' mode where supported. Note that some destructive commands, such as hard resets, are clearly marked and should only be used after you have verified your current working directory state. If you are dealing with production databases, ensure you have a fresh dump before running any recovery script provided by the agent. Remember, the agent's primary goal is to return your environment to a stable, known-good state with minimal data loss.

Metadata

Stars2387
Views0
Updated2026-03-09
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-gitgoodordietrying-emergency-rescue": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#git#recovery#debugging#devops#emergency
Safety Score: 2/5

Flags: file-read, file-write, code-execution