본문으로 건너뛰기
TakoAPI
스킬로 돌아가기

emergency-rescue

gitgoodordietrying 제작

Git & GitHub
2.4kclawskills.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 등 사용하는 코딩 에이전트에 붙여넣으세요.

링크