env-secrets-manager

You can scan source code and .env files for exposed secrets using pattern-based detection to identify suspicious tokens before merge. The skill classifies findings by severity and outputs JSON reports, enabling prioritized cleanup during repository hygiene checks.

Detecting leaked credentials in .env files requires pattern-based scanning of environment files and working trees to find unsafe configuration values. The process classifies risks by severity and provides reference guidance for validation, containment, and credential rotation.

Yes, you can use automated secret scanning as a CI/CD gatekeeping check. The skill supports pre-commit hooks and audit workflows by evaluating repository hygiene, detecting exposed secrets, and generating JSON output that can be parsed by continuous integration pipelines.

Handling credential rotation after an environment file leak involves following reference guidance for containment and follow-up steps. The skill provides rotation-ready instructions to validate exposed tokens, contain the breach, and update unsafe configuration values across development and production.

Yes, secret scanning works for both local development reviews and incident response workflows. The skill audits repository working trees and environment files for exposed secrets, applying severity classification and JSON output to support both preventative checks and reactive incident handling.