env-checklisted

# Purpose Audit environment variables across all of the project's repositories (see `.claude/project.json` → `repos`) to find missing, unused, undocumented, or inconsistent env vars and flag security issues. Produce a structured markdown report with file:line citations. Related skills: `gcp-cicd-auth` (for cloud credential variables), `deployment` (for CI/CD variable plumbing and runtime values injection). # When to use this skill - Add or remove an env var in any of the project's repos and verify cross-repo consistency - Prepare a release and confirm all required env vars are documented in `env.example` - Review a PR that touches `values.yaml`, `env.example`, `getServerEnv()`, or `clientEnv` - Investigate a deployment failure caused by a missing or misspelled env var # When NOT to use this skill - Checking which env vars are populated in a running cluster or pod -- requires exec access to the running service, not static analysis - Adding a new secret to the cloud provider's secret manager -- use `gcp-cicd-auth` - Reviewing Prisma schema, API routes, or any non-env-var code - Writing unit tests that use env var fixtures -- test fixtures intentionally use placeholder values # Required environment (Runtime: .claude/skills/env-check/SKILL.md) - Tools/libraries: Read, Grep, Glob (no write access) - Repos in scope: the project's canonical repo list from `.claude/project.json` → `repos`, plus the device/edge repo (`device`) if the project has one. Typical shape: the main app