What problem does it solve? Agents with repository access can accidentally read live credentials from .env files and write them into committed files, leaking secrets into git history. This Skill enforces strict prohibitions and safe alternatives to prevent credential exposure. ## Core Features & Use Cases - Prohibited File Rules: Blocks reading of .env, .env.local, .env.production, and other .env.* variants while allowing safe templates like .env.example. - Secret Pattern Detection: Provides regex patterns to detect API keys, passwords, connection strings, JWT tokens, private keys, AWS credentials, and email addresses before commits. - Pre-Commit Validation: Defines a blocking validation workflow that scans staged files, halts commits containing secrets, and reports violations to the user. - Use Case: Before committing team decision logs to git, an automated commit process scans staged content for credential patterns, blocks the commit if a database connection string is found, and instructs the user to replace it with a placeholder. ## Quick Start Scan my staged git changes for any secrets or credentials before committing and block the commit if any are found.
