env-manager

name	env-manager
description	Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms
version	1.0.0
category	infrastructure
progressive_disclosure	{"entry_point":{"summary":"Validate, synchronize, and secure environment variables across local dev, CI/CD, and deployment platforms with framework-specific support","when_to_use":"When managing .env files, deploying to Vercel/Railway/Heroku, syncing with secret managers, or troubleshooting env-related issues","quick_start":"1. Validate local .env 2. Check security 3. Sync to platform 4. Verify deployment 5. Generate documentation"},"references":["validation.md","security.md","synchronization.md","frameworks.md","troubleshooting.md"]}
author	Claude MPM Team
license	MIT
requires_tools	["bash","python"]
tags	["environment-variables","deployment","security","devops","nextjs","vercel","railway"]
context_limit	800
effort	medium

Environment Variable Manager

Overview

Manage environment variables systematically across local development, CI/CD pipelines, and deployment platforms. Prevent common issues like missing variables, exposed secrets, platform misconfigurations, and framework-specific gotchas.

Core capabilities:

• Validation: Check structure, completeness, naming conventions
• Security: Scan for exposed secrets, validate .gitignore coverage
• Synchronization: Sync with deployment platforms and secret managers
• Framework Support: Next.js, Express, Flask, Django patterns
• Documentation: Auto-generate .env.example and setup guides

When to Use This Skill

Activate when:

• Setting up new project environment configuration
• Deploying to Vercel, Railway, Heroku, or other platforms
• Troubleshooting "works locally but not in production"
• Managing secrets across multiple environments
• Syncing variables with 1Password, AWS Secrets Manager
• Creating .env.example documentation
• Onboarding new developers (environment setup)
• Migrating between deployment platforms
• Framework-specific env configuration (Next.js NEXT_PUBLIC_ prefix)

Core Principles

1. Never Log Secrets: All operations must NEVER display actual secret values
2. Validate Before Deploy: Catch env issues locally, not in production
3. Framework-Aware: Respect framework conventions (Next.js, Express, Flask)
4. Platform-Specific: Generate correct configs for each deployment platform
5. Security First: Scan for exposed secrets, validate .gitignore

Quick Start

Validation Workflow

# 1. Check local .env structure
python scripts/validate_env.py .env

# 2. Check for missing variables
python scripts/validate_env.py .env --compare .env.example

# 3. Validate naming conventions
python scripts/validate_env.py .env --framework nextjs

# 4. Check for duplicates
python scripts/validate_env.py .env --check-duplicates