railway-environment

# Environment Configuration Query, stage, and apply configuration changes for Railway environments. ## Shell Escaping **CRITICAL:** When running GraphQL queries via bash, you MUST wrap in heredoc to prevent shell escaping issues: ```bash bash <<'SCRIPT' ${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh 'query ...' '{"var": "value"}' SCRIPT ``` Without the heredoc wrapper, multi-line commands break and exclamation marks in GraphQL non-null types get escaped, causing query failures. ## When to Use - User wants to create a new environment - User wants to duplicate an environment (e.g., "copy production to staging") - User wants to switch to a different environment - User asks about current build/deploy settings, variables, replicas, health checks, domains - User asks to change service source (Docker image, branch, commit, root directory) - User wants to connect a service to a GitHub repo - User wants to deploy from a GitHub repo (create empty service first via railway-new skill, then use this) - User asks to change build or start command - User wants to add/update/delete environment variables - User wants to change replica count or configure health checks - User asks to delete a service, volume, or bucket - User says "apply changes", "commit changes", "deploy changes" - Auto-fixing build errors detected in logs ## Create Environment Create a new environment in the linked project: ```bash railway environment new <name> ``` Duplicate an existing environment: ```bash rail...