Git Leak Recovery FAQs

Question 1

Why is the cleanup order important in this skill?

Accepted Answer

Git's garbage collection (GC) will not remove 'unreachable' objects if they are still referenced in the reflog. This skill ensures Claude expires the reflog first, allowing the subsequent aggressive GC to actually purge the sensitive data from disk.

Question 2

How does this skill improve my developer workflow?

Accepted Answer

It automates the complex reconnaissance needed to find dangling commits and unreachable objects. By providing a standardized cleanup sequence, it ensures you don't miss hidden data in stashes or reflogs that standard deletions might overlook.

Question 3

What Git capabilities does it provide?

Accepted Answer

The skill includes advanced workflows for analyzing the Git reflog, using fsck to find unreachable objects, extracting files from specific commit hashes without checkouts, and executing multi-step verification to confirm secret removal.

Question 4

When should I use this skill?

Accepted Answer

Use this skill if you accidentally committed sensitive credentials, lost work after a 'git reset' or 'git rebase', or need to ensure a repository is completely sanitized before being made public.

Question 5

What does the Git Leak Recovery skill do?

Accepted Answer

This skill provides specialized workflows for Claude Code to identify and recover sensitive data (like API keys or lost commits) from Git's underlying object storage. It also guides the permanent, secure removal of that data through aggressive garbage collection and reflog expiration.

Git Leak Recovery

Git Leak Recovery

Características Principales

Casos de Uso

Características Principales

Casos de Uso