pii-sweep

What problem does it solve?

Detect and remediate personally identifiable information (PII), credentials, and internal references scattered across a repository before it is published or shared, reducing the risk of accidental data leaks or credential exposure.

Core Features & Use Cases

• Regex-based Sweeps: Detects emails, phone numbers, API keys, spreadsheet/document IDs, internal URLs, physical addresses, and user-supplied names across code, docs, and config files.
• Safe Review Workflow: Groups findings by category, presents contextual evidence, and requires explicit user classification (true positive, false positive, move to .env) before any changes.
• Non-destructive Replacement & Verification: Replaces confirmed PII with standardized placeholders, adds moved secrets to .env and .env.example, shows before/after diffs, and re-runs verification passes to achieve zero findings.
• Exclusions & Guardrails: Skips .git, node_modules, vendor, binaries, and lockfiles; warns about git history and recommends safe history-rewrite tools without performing destructive operations automatically.
• Use Case: Preparing a private repo for open-source release by scanning README, source files, and configuration to ensure no live keys or personal data remain.

Quick Start

Ask the skill to run a full PII sweep of the current repository and guide you through reviewing and replacing any findings.