Scans a git repo for hardcoded secrets, personal info, and sensitive data before it gets published. Checks both current files AND the full git commit history (because secrets in old commits are still exposed on push). Finds API keys, passwords, tokens, home directory paths with usernames, email addresses, private keys, database connection strings, and more. Reports findings by severity with exact file and line locations, and gives actionable remediation steps.
Use this skill whenever the user asks to: check if a repo is safe to publish/push/open-source, scan for secrets or credentials, check for personal info, audit before making a repo public, "is this ready to push?", "anything private in here?", or similar pre-publish safety checks. Also use it proactively when the user is about to push or publish a repo and hasn't explicitly asked for a security check — it's better to catch issues early.
2026-04-16