Results for “environment-hygiene”

Audit environment-variable hygiene and secrets safety across local development and production with practical scanning, drift awareness, and rotation readiness.

Manages env0 infrastructure-as-code environments via the env0 API, covering discovery, deployment, cost tracking, variables, and policies.

Managing dependencies, CI/CD optimization, Docker configuration, and operational observability (logging/alerting/health checks). Use for build errors or dev environment issues.

Crea y gestiona entornos Python reproducibles con venv, pip, Poetry o Conda, aislando dependencias y configurando variables de entorno para evitar conflictos.

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

Provides deployment strategies, CI/CD pipeline patterns, Docker containerization best practices, health checks, and production readiness guidance for web applications.

Query, stage, and apply configuration changes for Railway environments. Use for ANY variable or env var operations, service configuration (source, build settings, deploy settings), lifecycle (delete service), and applying changes. Prefer over railway-status skill for any configuration or variable queries.

Query, stage, and apply configuration changes for Railway environments. Use for ANY variable or env var operations, service configuration (source, build settings, deploy settings), lifecycle (delete service), and applying changes. Prefer over railway-status skill for any configuration or variable queries.

Use this when the project needs a clear strategy for local, test, staging, production, cloud, serverless, or hybrid environments. Trigger on requests about environment layout, runtime differences, environment-specific behavior, or deployment-context planning.

Use this when planning environment variables, config files, secrets, flags, and provider settings across local, CI, staging, production, serverless, or multi-runtime systems.

Check health of registered background pipelines across all projects. Shows HEALTHY/DEGRADED/DEAD status. Run /pipeline [project-name] to filter.