SIDDARTHA577/envguard-node / .agents/skills/envguard-review
envguard-review
UnverifiedReviews environment variable and secret handling in a project for common security vulnerabilities (e.g. unvalidated variables, console.log leaks, missing .gitignore rules, and unmasked error outputs).
envguard-review Skill
Conducts a security-focused review of environment variable management, secret handling, accidental leakage vectors, and configuration hygiene.
When to Trigger
- The user requests a security review of secrets or environment configuration.
- Checking for accidental credential leakage in log statements, error handlers, or git tracking.
- Pre-deployment security verification of
.gitignore,.dockerignore, and schema definitions.
When NOT to Trigger
- Penetration testing or active network exploitation of running services.
- General application business logic code reviews unrelated to secrets or configuration.
- Generating schemas from scratch without prior code audit (use
envguard-audit).
Supported Projects & Environments
- Any Node.js, TypeScript, or JavaScript application.
- Containerized workflows (Docker, Docker Compose).
- Serverless and cloud-native Node.js deployments.
Required Tools & Permissions
- Tools: Grep / file search, file reader (
read_file,run_command). - Permissions: Read-only access to repository source and configuration files.
Expected Inputs
- Repository source code directory.
- Configuration and ignore files (
.gitignore,.dockerignore, Dockerfiles, CI workflows).
Step-by-Step Workflow
Step 1: Verify Git & Container Ignore Rules
- Verify
.gitignoreexplicitly excludes.env,.env.*(except.env.example),*.pem,*.key, and*.local. - If Docker is used, verify
.dockerignoreexists and excludes secret and local environment files.
Step 2: Search for Sensitive Value Leaks
- Search for dangerous logging patterns:
console.log(process.env),logger.info(req.body), or custom logs echoing configuration. - Check exception classes and error handlers to ensure failed validations do not print secret values.
Step 3: Verify Startup Validation Coverage
- Inspect entry points to confirm required credentials (database URLs, API tokens, JWT keys) are validated at boot time.
- Verify that missing required variables halt startup immediately rather than causing runtime crashes later.
Step 4: Validate Sensitivity Tags
- Verify that all credentials, passwords, and private tokens in EnvGuard schemas use
.sensitive()to ensure redaction.
Validation Steps
- Verify
.gitstatus to ensure no tracked.envfiles are accidentally committed in git history. - Run
git ls-files | grep '\.env$'or similar to confirm clean repository tracking.
Expected Outputs
- A categorized security report:
- Critical Vulnerabilities: e.g. committed secret files, unmasked logging of credentials.
- Security Hardening Needs: e.g. unconstrained port types, unvalidated URLs, missing
.dockerignore. - Best Practice Recommendations: e.g. marking fields
.sensitive(), adding CI schema drift checks.
Failure Handling
- If git history cannot be inspected, clearly note the limitation in the final report.
- Clearly distinguish verified vulnerabilities from unverified static pattern warnings.
Safety & Privacy Boundaries
- NEVER display or print actual secrets discovered during review.
- NEVER transmit repository findings to external endpoints.
- Do not make exaggerated security claims (e.g. "100% secure" or "guaranteed unhackable").
Example User Prompts
- "Review my environment variable security and .gitignore with envguard-review"
- "Check this project for potential secret leakage in logs or error handling"
- "Verify environment configuration security before deployment"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |