Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    env example sync checker

    3

    Detect missing or orphaned environment variables by comparing .env.example against your source code.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    env example sync checker

    env example sync checker

    Example session with this skill installed

    Audit my .env.example file against the src/ directory and tell me if I've missed any variables or if any are no longer needed.

    • Read your context and instructions
    • Compiled the env example sync
    • Generated the document

    I have completed the audit comparing .env.example against the references found in your src/ directory and configuration files.

    .env.example Sync Report

    Summary
    .env.example variables: 8 | Referenced: 9 | Matched: 7 | Missing: 2 | Orphaned: 1 | Dynamic/unresolved: 1

    Missing Variables

    Variables found in source but missing from .env.example.

    VariableSourceContext
    STRIPE_WEBHOOK_SECRETsrc/api/webhooks.ts:12Missing in example
    REDIS_TLS_ENABLEDsrc/lib/redis.ts:4Missing in example

    Orphaned Variables

    Declared in .env.example but no references were found in the inspected source.

    VariableDeclared InNotes
    LEGACY_API_KEY.env.example:15Potentially deployment-managed or obsolete

    Dynamic / Unresolved

    Static analysis found environment access, but the variable names are determined at runtime.

    • process.env[prefix + "_TOKEN"] at src/auth/providers.ts:22

    Recommended Actions

    1. Add STRIPE_WEBHOOK_SECRET and REDIS_TLS_ENABLED to .env.example with placeholder values.
    2. Verify if LEGACY_API_KEY is used by CI/CD or external scripts before removal.
    3. Manually audit src/auth/providers.ts to ensure all dynamic token variants are documented.

    Next steps

    • Would you like me to append the missing variables to .env.example for you?
    • Should I check for these variables in docker-compose.yml or other config files?

    env-example-sync-checker.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Identify variables used in code but missing from .env.example.Find orphaned environment variables that are no longer referenced.Audit configuration files like docker-compose and Dockerfiles for env usage.Generate a sync report for repo onboarding and CI/CD maintenance.

    About this skill

    The problem

    Developers often forget to update .env.example when adding new environment variables to source code. This leads to broken onboarding experiences for new contributors and missing configuration in CI/CD pipelines.

    What it does

    • Scans source code for process.env, os.environ, and language-specific equivalents to identify required variables.
    • Parses .env.example to extract declared variable names while ignoring their values.
    • Identifies missing variables that are used in code but absent from the example file.
    • Flags orphaned variables present in the example file but not found in the codebase.
    • Detects dynamic environment access that cannot be statically analyzed for manual review.

    Frameworks & tools

    Works with Node.js, Python, Ruby, PHP, Go, Java, and Rust. Supports framework conventions for Next.js and Vite.

    Why this beats prompting it yourself

    Generic prompts often hallucinate environment variable names or fail to scan configuration files like docker-compose.yml. This skill follows strict security protocols to never leak or display actual secret values during the audit process.

    Use cases

    • Pre-commit audits to ensure .env.example stays in sync with feature branches.
    • Onboarding troubleshooting when a project fails to start due to missing config.
    • Cleaning up legacy repositories by identifying potentially obsolete environment declarations.

    Known limitations

    Static analysis cannot detect variables accessed via dynamic string concatenation or runtime reflection. It does not scan for actual secrets or validate credential correctness.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 6 days ago

    • Passed all security checks, Safe to install

    Listed6 days ago
    Updated1 day ago

    Frequently Asked Questions