Slash Command

/sync-env

Synchronizes environment variables across dev, staging, and production by scanning code/.env files, identifying discrepancies/unused vars, generating updated .env.example, and reporting changes.

Javascript

Python

Git

devops

automation

npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin env-sync

Popularity

Parent stars

1,716

Parent forks

535

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/env-sync:sync-env

Model invocable

No pre-commands

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

# /sync-env - Sync Environment Variables

Synchronize environment variables across development, staging, and production.

## Steps

1. Read the current .env file and .env.example for the project
2. Identify all environment variables used in the codebase (process.env, os.environ)
3. Compare variables across environments: development, staging, production
4. Identify missing variables in each environment
5. Identify variables present in code but missing from all .env files
6. Detect variables in .env files that are no longer used in code
7. Verify variable naming conventions are consistent (UP...

Command Content

29 lines · ~377 tokens

Other plugins with /sync-env

/env-setup

Sets up and audits environment variables for a service across local, Railway, and AWS. Generates .env.example, validates required vars, flags missing ones. Supports local, railway, aws, audit modes.

ai-toolkit

/env

165

Manages Vercel project environment variables: list by environment, pull to local .env files, add/remove with production confirmation, diff local vs remote.

vercel

/env-validator

Validates .env files against schemas with type checking, required vars verification, format validation, security scans. Generates .env.example, checks missing vars, supports compare.

6 tools

env-validator

/env-setup

1.7k

Generates .env.example from templates or code analysis with categorized vars and comments, creates .env if missing with prompts, verifies .gitignore, adds TypeScript/Python runtime validation.

env-manager

/sync-dev

[DEPRECATED] Synchronizes development environment by detecting conflicts in dependencies, configs, migrations, artifacts; validates syntax and recommends fixes. Use /sync --env.

autonomous-dev

/env-config-manager

Manages environment configs and secrets with Vault, AWS Secrets Manager, Azure Key Vault; initializes .env setups, validates variables, generates TypeScript types, rotates secrets.

6 tools

env-config-manager

Stats

LanguageJavaScript

Parent stars1,716

Parent forks535

MaintenanceFair

Last CommitFeb 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

# /sync-env - Sync Environment Variables Synchronize environment variables across development, staging, and production. ## Steps 1. Read the current .env file and .env.example for the project 2. Identify all environment variables used in the codebase (process.env, os.environ) 3. Compare variables across environments: development, staging, production 4. Identify missing variables in each environment 5. Identify variables present in code but missing from all .env files 6. Detect variables in .env files that are no longer used in code 7. Verify variable naming conventions are consistent (UP...

/sync-env - Sync Environment Variables

Synchronize environment variables across development, staging, and production.

Steps

Read the current .env file and .env.example for the project

Identify all environment variables used in the codebase (process.env, os.environ)

Compare variables across environments: development, staging, production

Identify missing variables in each environment

Identify variables present in code but missing from all .env files

Detect variables in .env files that are no longer used in code

Verify variable naming conventions are consistent (UPPER_SNAKE_CASE)

Check for sensitive variables that should use secrets management

Generate an updated .env.example with all required variables and descriptions

Sync missing variables to target environments (with placeholder values for secrets)

Report: variables added, removed, mismatched across environments

Update documentation with the current environment variable inventory

Rules

Never copy secret values between environments; use placeholders

Always update .env.example when adding new variables

Do not commit .env files to version control; verify .gitignore includes them

Flag variables with default values that look like real credentials

Group related variables together in .env files (database, API keys, feature flags)

Validate variable values against expected formats (URLs, numbers, booleans)

Include comments in .env.example explaining each variable's purpose

/sync-env - Sync Environment Variables

Synchronize environment variables across development, staging, and production.

Steps

Read the current .env file and .env.example for the project
Identify all environment variables used in the codebase (process.env, os.environ)
Compare variables across environments: development, staging, production
Identify missing variables in each environment
Identify variables present in code but missing from all .env files
Detect variables in .env files that are no longer used in code
Verify variable naming conventions are consistent (UPPER_SNAKE_CASE)
Check for sensitive variables that should use secrets management
Generate an updated .env.example with all required variables and descriptions
Sync missing variables to target environments (with placeholder values for secrets)
Report: variables added, removed, mismatched across environments
Update documentation with the current environment variable inventory

Rules

Never copy secret values between environments; use placeholders
Always update .env.example when adding new variables
Do not commit .env files to version control; verify .gitignore includes them
Flag variables with default values that look like real credentials
Group related variables together in .env files (database, API keys, feature flags)
Validate variable values against expected formats (URLs, numbers, booleans)
Include comments in .env.example explaining each variable's purpose

/sync-env

Popularity

Invocation

Context Preview

Command Content

Other plugins with /sync-env

Help us improve

Help us improve

Find plugins for your project

/sync-env

Popularity

Invocation

Context Preview

Command Content

/sync-env - Sync Environment Variables

Steps

Rules

Other plugins with /sync-env

Help us improve

/sync-env - Sync Environment Variables

Steps

Rules