本文へスキップ
TakoAPI
スキル一覧に戻る

emergency-rescue

gitgoodordietrying 作

Git & GitHub
2.4kダウンロード数はclawskills.shが公開している値です
1スター
1閲覧数
0件のいいねサインインするとこのスキルにいいねできます
—まだ評価がありません
あなたの評価

概要

Recover from developer disasters.

説明

このスキルでできること

Step-by-step recovery procedures for common developer disasters: force-pushed branches, leaked credentials, full disks, failed database migrations, broken deploys, and lost SSH access. Each section follows a diagnose, fix, verify sequence. Commands are non-destructive by default, with destructive steps clearly flagged.

Having all recovery procedures in one place with a consistent diagnose-fix-verify structure means less time searching documentation during an active outage.

使いどころ

  • Recovering lost commits after an accidental git reset --hard
  • Revoking and purging a leaked API key from public git history
  • Freeing disk space when Docker images exhaust a drive
  • Rolling back a broken production deployment to a known-good state
  • Regaining SSH access to a cloud server after a lockout

ワークフロー例

入力

User asks: I accidentally committed my AWS secret key to a public GitHub repo

エージェント
  1. 1

    Identify the file and commit containing the exposed credential using git log

  2. 2

    Revoke the AWS access key immediately via the AWS IAM console before touching git

  3. 3

    Remove the file from git tracking and add it to .gitignore

  4. 4

    Rewrite git history with git filter-repo to permanently remove the secret from all commits

  5. 5

    Force push the cleaned history to the remote and instruct all collaborators to re-clone

出力

Credential revoked, git history cleaned of the secret, .gitignore updated to prevent recurrence, collaborators notified to re-clone

インストール

clawhub install gitgoodordietrying/emergency-rescue

CLIコマンドを実行するか、Claude Code、Cursor、Codexなどお使いのコーディングエージェントにプロンプトを貼り付けてください。

リンク