What problem does it solve? Leaked credentials hide in source files, configs, and especially git history, where a secret removed in a later commit remains fully exposed. This Skill finds exposed API keys, tokens, and private keys before attackers do, then drives the rotation procedure so the leak is actually remediated rather than just deleted from the current tree. ## Core Features & Use Cases - Three-layer scanning: grep-based pattern detection for AWS, OpenAI, GitHub, Slack, Google, and Telegram credentials across the working tree, plus git-history scanning and a manual configuration review covering .gitignore, Dockerfiles, CI, logs, and frontend bundles. - Rotation procedure: ordered steps to rotate first, assess blast radius via provider audit logs, scrub history with git filter-repo, and add pre-commit hooks and CI scanning to prevent recurrence. - Severity model and report template: Critical/High/Medium/Low classification with a structured Markdown findings table that never exposes full secret values. - Use Case: Before open-sourcing a repository, run the audit to catch an AWS key committed six months ago, rotate it, scrub history, and add a gitleaks pre-commit hook. ## Quick Start Audit this repository for exposed secrets in the working tree and git history, then report findings by severity with rotation steps.
