db-env-switch

To safely switch database configurations, this skill detects the current environment, enforces confirmation prompts for production changes, updates .env.local, and terminates active processes to ensure a clean reload of development services.

Killing Vite and worker processes during an environment switch prevents stale configuration variables from persisting in memory, ensuring that your development services load the updated local or production database settings from .env.local.

Environment detection works by reading the current LOCAL or PRODUCTION status directly from your .env.local file, enabling the skill to determine the active database configuration before initiating any switch or safety approvals.

No, you cannot automate production environment updates without manual confirmation. The skill deliberately enforces safety approval prompts when switching to production to prevent accidental data exposure or unauthorized configuration changes.

When toggling to production, your dotenv file is automatically updated to flip the environment settings from LOCAL to PRODUCTION, after which the skill terminates running processes and provides restart guidance for your services.

A key limitation is that process management requires manual restarts. While the skill updates .env.local and terminates Vite and worker processes, you must manually execute the provided restart commands to resume development services.