env-var-manager

Synchronize environment variables across project files and deployment configurations.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/WebDev70/hosting-google --skill env-var-manager
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: env-var-manager
Source: https://github.com/WebDev70/hosting-google/tree/main/.claude/skills/env-var-manager
Command: npx skills add https://github.com/WebDev70/hosting-google --skill env-var-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of keeping environment variables synchronized across a project's multiple files and deployment configurations, reducing misconfigurations and rollout errors.

Core Features & Use Cases

  • Global consistency: Guidance to propagate new variables across .env.example, server.js, and deployment files.
  • Documentation alignment: Updates to docs/ENVIRONMENT-VARIABLES.md and CLAUDE.md to reflect current variables.
  • Security-conscious practices: Promotes not committing secrets and using secret managers in production.

Quick Start

Create or update ENV vars in .env.example, ensure server.js reads the variables, and document the changes in ENVIRONMENT-VARIABLES.md and CLAUDE.md.

Frequently Asked Questions about env-var-manager

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

FAQPage Schema
How do I keep environment variables synchronized across multiple project files?▼

To keep environment variables synchronized across multiple project files, this Skill provides a workflow to propagate updates through .env.example, server.js, docker-compose.yml, and Dockerfile, reducing deployment misconfigurations.

What is the best way to document environment variables in a Node.js project?▼

The best way to document environment variables is by updating docs/ENVIRONMENT-VARIABLES.md and CLAUDE.md alongside code changes, ensuring centralized documentation accurately reflects current variables required by server.js.

How do I safely update a PORT environment variable for deployment?▼

To safely update a PORT environment variable for deployment, you must align configurations across .env.example, server.js, docker-compose.yml, and Dockerfile, outlining required defaults and validation steps to prevent rollout errors.

Does this workflow support updating deployment configurations for Docker?▼

Yes, the workflow supports Docker by requiring updates to docker-compose.yml and Dockerfile when introducing new environment variables, ensuring containerized deployment configurations remain aligned with application code.

When do I need to update .env.example when adding new environment variables?▼

You need to update .env.example immediately when adding new environment variables to ensure required defaults are visible, enforcing a safe workflow by validating steps and aligning centralized documentation before deployment.