mgiovani/ai-arsenal / skills/env-setup
env-setup
VerifiedScans a codebase for environment variable usage to generate or sync .env.example, validate .env completeness against what the code actually reads, and detect leaked secrets in .env or git history. Use for "/env-setup", "update .env.example", "sync .env.example with the codebase", "check if .env has everything it needs", "is .env in .gitignore", or "scan for leaked secrets in .env". Not a full security audit (use review-security for OWASP-level scanning) and not a generic secret-rotation or CI-secrets-injection tool.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.3 KB |
| evals/evals.json | config | 3.6 KB |
| evals/trigger-eval.json | config | 2.0 KB |
| references/env-example-template.md | markdown | 1.7 KB |
| references/scan-patterns.md | markdown | 2.3 KB |
evals/trigger-eval.json
View on GitHub[
{"query": "can you scan the repo and update .env.example, I added a few new vars", "should_trigger": true},
{"query": "/env-setup", "should_trigger": true},
{"query": "/env-setup validate", "should_trigger": true},
{"query": "check if my .env is missing anything the code actually needs", "should_trigger": true},
{"query": "sync .env.example so it matches what's actually used in the codebase", "should_trigger": true},
{"query": "scan for leaked secrets in .env, I think we committed one by accident", "should_trigger": true},
{"query": "is .env actually in our .gitignore? double check please", "should_trigger": true},
{"query": "generate a .env.example for this new service from scratch", "should_trigger": true},
{"query": "there are a bunch of stale env vars in .env.example nobody uses anymore, clean it up", "should_trigger": true},
{"query": "run env-setup scan --check-secrets on this repo before we deploy", "should_trigger": true},
{"query": "do a full OWASP-style security audit of this codebase", "should_trigger": false},
{"query": "review this PR for security vulnerabilities before I merge it", "should_trigger": false},
{"query": "the app crashes on startup because STRIPE_SECRET_KEY is undefined, fix the bug", "should_trigger": false},
{"query": "implement a new config loader that reads settings from a YAML file", "should_trigger": false},
{"query": "write a conventional commit message for these .env.example changes", "should_trigger": false},
{"query": "initialize documentation structure for this new project", "should_trigger": false},
{"query": "set up a GitHub Actions CI workflow that injects secrets from repo settings", "should_trigger": false},
{"query": "refactor how we load configuration across the services", "should_trigger": false},
{"query": "add a Dockerfile and docker-compose.yml for local dev", "should_trigger": false},
{"query": "rotate our AWS access keys since one may have leaked", "should_trigger": false}
]
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: 471k | 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: 471k | 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: 471k | 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: 194k | Updated | Claude CodeCodex | Verified | Install |