What problem does it solve? Repositories pushed to public remotes often leak API keys, tokens, .env files, internal URLs, IP addresses, and personal or employer data. This Skill detects both machine secrets and organizational data before code goes public, and blocks unsafe commits automatically. ## Core Features & Use Cases - Secret Detection: Scans staged diffs and filenames for provider keys (sk-, sk_live_, whsec_), JWTs, database URLs with embedded credentials, and key/cert files (.pem, .key, .p12, id_rsa). - Private Data Auditing: Flags internal hostnames, private IP ranges (10.x, 192.168.x, 172.16-31.x), real personal data in fixtures, and employer/client references. - Automation: Ships an installable pre-commit hook that blocks unsafe commits and a strong .gitignore baseline covering env, key, backup, and dump patterns. - Use Case: Before open-sourcing a side project, run the scan to catch a leftover sk_live_ key in config.py and real customer emails in seed.sql, then rotate, redact, and generalize before pushing. ## Quick Start Scan my repository for secrets, credentials, and private data, then install the pre-commit hook and update my .gitignore before I make it public.