skills.rest
leandro-br-dev
leandro-br-devCOMMUNITY
Explore all skills by this author →
GitHub

production-env-sync

Validate and synchronize production environment variables via SSH deployment.

Updated Aug 27, 2026
Search Tags:#deployment#production#ssh#backups#env-sync#env-compare
One-click install
npx skills add https://github.com/leandro-br-dev/charhub --skill production-env-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: production-env-sync
Source: https://github.com/leandro-br-dev/charhub/tree/main/docs/agents/reviewer/skills/production-env-sync
Command: npx skills add https://github.com/leandro-br-dev/charhub --skill production-env-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that production environment configuration is complete and aligned with local definitions, preventing deploy-time failures due to missing or outdated keys.

Core Features & Use Cases

  • Pre-deployment validation of root and per-service env files (.env, backend/.env, frontend/.env.production) against required keys
  • Dry-run capable comparison and planning to identify differences without altering production
  • Secure, auditable sync to production with automatic remote backups and post-sync verification

Quick Start

Validate local keys with the dry-run option to see what would be synced, then run the live-sync after confirmation.

Frequently Asked Questions about production-env-sync

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

FAQPage Schema
How do I validate environment variables before deploying to production?▼

Pre-deploy env validation checks that .env.production contains all required keys across root and backend/frontend directories. This ensures local definitions align with production, preventing deploy-time failures from missing or outdated keys.

Can I dry-run environment variable synchronization to see what would change on the server?▼

Yes, a dry-run comparison identifies differences between local and production environment variables without altering the server. You can review the planned changes and run the live-sync only after confirming the differences.

Does production env sync support remote SSH deployment and automatic backups?▼

Production environment synchronization integrates with remote SSH deployment and creates automatic remote backups before applying changes. Post-sync verification ensures the production environment variables are correctly updated on the server.

What is the best way to keep root and per-service env files aligned during environment changes?▼

Enforcing key presence across root and per-service env files like backend/.env and frontend/.env.production keeps configurations aligned. Running a validation check during environment changes ensures all services have the required keys before pushing updates.

How do I push environment variable updates to a production server without causing downtime?▼

Pushing environment updates via SSH with a dry-run planning phase prevents downtime by identifying missing keys beforehand. Automatic remote backups and post-sync verification ensure the production server remains stable during the update.

Related Skills

Explore More Software Engineering Skills→
jholhewresjholhewres
14

execution

Execute shell commands and transfer files via SSH and SCP.

Official
Intermediate
zhangzhang-111-izhangzhang-111-i
2

senior-devops

Automates CI/CD pipeline generation, Terraform module scaffolding, and deployment orchestration with rollback.

Community
Advanced
jabrenajabrena
423

055-design-parallel-change

Design parallel change strategies for database schema and data migrations.

Community
Advanced
BarisSozenBarisSozen
1

pitfalls-security

Guide secure handling of session keys, secrets, and environment data.

Community
Intermediate