Git Repository Sanitization FAQs

Question 1

What does the Git Repository Sanitization skill do?

Accepted Answer

This skill provides a systematic approach to identifying and removing sensitive credentials, API keys, and private tokens from your project. It uses multi-strategy detection, including pattern matching and entropy analysis, to ensure no secrets are left exposed in your codebase.

Question 2

When should I use this skill with Claude Code?

Accepted Answer

You should use this skill when preparing a private repository for public release, auditing for credential exposure, cleaning up after a leak, or performing a compliance review. It is essential for any task involving the removal of sensitive data from version control.

Question 3

Does it clean my Git history or just current files?

Accepted Answer

It handles both. The skill provides strategies for sanitizing your active working directory and offers specialized guidance for deep cleaning Git history using tools like BFG Repo-Cleaner or git-filter-repo to ensure secrets don't persist in hidden objects.

Question 4

How does this skill help prevent false positives?

Accepted Answer

The skill follows a systematic verification process that categorizes findings, checks for environment variable references versus actual values, and documents all potential secrets before modification. This ensures that only sensitive data is removed while maintaining configuration integrity.

Question 5

What happens to the code after secrets are removed?

Accepted Answer

The skill implements standardized placeholders (like <your-api-key>) to maintain file validity and configuration structure. It also provides a post-sanitization checklist to verify file syntax and recommends credential rotation for any exposed secrets.

Git Repository Sanitization

Git Repository Sanitization

주요 기능

사용 사례

주요 기능

사용 사례