restart-dev-containers

Restart development containers by running bash .claude/skills/restart-dev-containers/execute.sh from your project root. The script stops containers, rebuilds using the dev overlay (docker-compose.yml + docker-compose.dev.yml), verifies compilation, and checks service health endpoints to ensure a clean, verified state.

The dev overlay applies development-specific configuration on top of the base docker-compose.yml, enabling isolated dev containers under the -p witchcityrope-dev flag. This keeps development and test environments separate while ensuring proper compilation checks and health verification post-restart.

Restart dev containers when code changes require a rebuild, containers become unhealthy, or E2E tests fail. A full container restart with the dev overlay ensures clean builds and verified compilation, not just service restarts which may skip necessary rebuild steps.

Docker must be running, you must execute from the project root directory, and the dev overlay file (docker-compose.dev.yml) must be present. The script validates these prerequisites before proceeding with container stop, rebuild, and health checks.

Set the environment variable SKIP_CONFIRMATION=true before running the script: SKIP_CONFIRMATION=true bash .claude/skills/restart-dev-containers/execute.sh. This bypasses the interactive confirmation while maintaining all prerequisite checks and health verification.

Post-restart verification includes compilation success checks and health endpoint validation for Web/API and database services. These quality checks confirm containers are not only running but properly built and ready to handle requests.