env-secrets-manager

Audits .env hygiene and detects secret leaks in repositories and CI pipelines.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/devCharuzu/philfida-taskmanage --skill env-secrets-manager-devcharuzu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-secrets-manager
Source: https://github.com/devCharuzu/philfida-taskmanage/tree/main/.windsurf/skills/env-secrets-manager
Command: npx skills add https://github.com/devCharuzu/philfida-taskmanage --skill env-secrets-manager-devcharuzu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Env and secrets drift and leakage across local development and production workflows, leading to credentials exposure and misconfigurations.

Core Features & Use Cases

  • Auditing .env/.env.* hygiene and ensuring proper gitignore recommendations.
  • Secret leak detection in repository working trees and CI contexts.
  • Rotation readiness guidance and containment pointers for incident response.

Quick Start

Run the env_auditor.py script on a repository to scan for likely secrets and output results in JSON for CI pipelines.

Frequently Asked Questions about env-secrets-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan .env files for secret leaks before deploying?

To scan .env files for secret leaks, run the env_auditor.py script on your repository. It flags sensitive patterns in environment variables and outputs results in JSON format suitable for CI pipeline checks.

What is env-var hygiene and why does it matter for CI pipelines?

Env-var hygiene involves preventing credential drift and leakage across local and production environments. It matters for CI pipelines because misconfigurations lead to exposed secrets, which this Skill detects by flagging sensitive patterns during deployment checks.

Can I integrate secret rotation readiness checks into my existing CI workflows?

Yes, you can integrate secret rotation readiness checks into CI workflows. The Skill outputs JSON results from scanning env files, allowing pipelines to enforce rotation readiness and provide containment pointers for incident response.

Does this approach detect secrets in both local development and production configurations?

Yes, this approach detects secrets in both local development and production configurations. It audits working trees and deployment configurations by scanning env files, ensuring drift awareness and flagging sensitive patterns across all workflows.

What is the best way to ensure .env files are properly ignored in git?

The best way to ensure .env files are ignored is by auditing .env hygiene and applying proper gitignore recommendations. The Skill scans repository working trees to flag sensitive patterns and prevent accidental secret leakage into version control.

What limitations exist when remediating secret drift across multiple environments?

When remediating secret drift, the Skill provides rotation readiness guidance and containment pointers rather than automated remediation. It focuses on auditing and flagging sensitive patterns in env files, leaving actual credential rotation to incident response procedures.