secret-detection

To scan git history for hardcoded secrets, the secret-detection skill reviews committed files and historical logs to uncover previously removed credentials. It then provides step-by-step remediation guidance including credential rotation and environment variable migration.

To set up a pre-commit hook for credential scanning, this skill generates pre-commit hook examples that automatically check source files for hardcoded API keys and tokens, preventing future secret leaks before they enter the repository.

The best way to find hardcoded passwords before an open-source release is to run a comprehensive security audit using the secret-detection skill, which scans source code across multiple languages for common secret patterns and sensitive file types.

Yes, you can use the secret detection skill for environment variable migration. It detects compromised credentials in codebases and provides explicit remediation guidance to rotate secrets, update .gitignore files, and migrate hardcoded values to environment variables.

Yes, the secret detection skill requires access to repository files and git logs to effectively scan source code and review commit history for hardcoded secrets, tokens, and passwords that may have been leaked previously.