Vai al contenuto
TakoAPI
Torna alle skill

emergency-rescue

di gitgoodordietrying

Git & GitHub
2.4kDownload riportati da clawskills.sh
1Stelle
1Visualizzazioni
0 likeAccedi per mettere like a questa skill
—Non ancora valutato
La tua valutazione

Sintesi

Recover from developer disasters.

Descrizione

Cosa fa questa skill

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.

Quando usarla

  • 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

Esempio di workflow

INPUT

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

AGENT
  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

OUTPUT

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

Installazione

clawhub install gitgoodordietrying/emergency-rescue

Esegui il comando CLI oppure incolla il prompt in Claude Code, Cursor, Codex o nell'agente di coding che usi.

Link