env-secrets-manager

Run a repository-wide audit to detect exposed environment variables, hard-coded credentials, and misconfigured secrets. The scan classifies leaks by severity (Critical, High, Medium, Low) and suggests specific remediation steps to minimize exposure risk across development, CI/CD, and production workflows.

Validate .env file structure by checking .env.example safety, confirming .gitignore coverage, and detecting missing or mismatched environment variables. This environment validation prevents accidental secret exposure and ensures configuration consistency across your development and deployment environments.

Implement secret rotation workflows using the provided containment steps, rotation plans, and CI/CD integration points. The Skill recommends cloud-native secret stores and policy-driven access control with auditing to enforce secret hygiene and enable safe credential rotation.

Yes, it audits and secures environment variables and secrets across development, testing, and production environments. It applies policy guidance, rotation planning, and secure storage best practices uniformly to prevent leaks, hard-coded credentials, and misconfigurations throughout the entire workflow.

Environment variable mismatches occur when .env structure is invalid or .env.example lacks proper coverage. The Skill validates .env files, checks .gitignore entries, and detects missing variables to ensure configuration consistency and prevent deployment failures caused by incomplete secret mappings.

Relying solely on .env files risks accidental exposure if .gitignore coverage is incomplete or if secrets are hard-coded. The Skill recommends transitioning to cloud-native secret stores with policy-driven access control and auditing to enforce stronger secret hygiene and compliance.