Secrets Validator

Prevent secrets from being committed by integrating pre-write hooks that scan files for high-severity patterns like AWS keys, GitHub tokens, private keys, and database URLs before commits succeed. The Skill blocks commits containing exposed secrets and guides you toward secure alternatives like environment variables and .env templates.

Detection covers AWS keys, GitHub tokens, private keys, database URLs, API keys, and other credentials across config, YAML, JSON, and environment files. The Skill classifies findings by severity—high, medium, and low—and applies regex-based patterns to identify diverse secret formats.

Yes, the Skill integrates across CI/CD, code reviews, and development workflows to scan all new or modified files for secrets. It provides structured remediation guidance and blocks high-severity findings automatically to prevent leaks before they propagate.

Store secrets in environment variables, use .env.example templates as safe configuration blueprints, and configure .gitignore to prevent credential files from reaching version control. The Skill emits specific remediation recommendations for each detected secret.

High-severity findings like AWS keys and private keys trigger immediate blocking to prevent exposure. Medium and low-severity patterns receive guidance but allow conditional processing, enabling flexible workflows while protecting critical credentials.