restart-dev-containers

Name: restart-dev-containers
Availability: InStock
Author: darkmonkdev

Restart WitchCityRope development containers with the dev overlay and health checks.

1|1|Updated Jun 28, 2025

Search Tags:#docker #containers #compilation #dev-ops #health-checks

Ready to run

npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill restart-dev-containers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: restart-dev-containers
Source: https://github.com/DarkMonkDev/WitchCityRope/tree/main/.claude/skills/restart-dev-containers
Command: npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill restart-dev-containers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, docker-compose.

What problem does it solve?

Reboots development containers using the correct overlay to ensure clean builds, proper compilation checks, and verified health endpoints.

Core Features & Use Cases

Dev-only isolation: Uses project flag -p witchcityrope-dev to keep dev and test containers separate.
Dev overlay restart: Starts containers with docker-compose.yml + docker-compose.dev.yml.
Quality checks: Verifies compilation and health of Web/API and database endpoints.

Quick Start

From project root, run:

bash .claude/skills/restart-dev-containers/execute.sh To skip confirmation:
SKIP_CONFIRMATION=true bash .claude/skills/restart-dev-containers/execute.sh

Frequently Asked Questions about restart-dev-containers

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

FAQPage Schema

How do I restart development containers with Docker Compose?▼

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.

What does the dev overlay do when restarting containers?▼

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.

When should I restart my dev containers instead of just restarting services?▼

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.

What prerequisites does Docker container restart require?▼

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.

How do I skip the confirmation prompt when restarting containers?▼

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.

What health checks run after restarting dev containers?▼

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.