skills.rest
DarkMonkDev
DarkMonkDevCOMMUNITY
Explore all skills by this author →
GitHub

restart-test-containers

Restart WitchCityRope test containers with docker-compose test overlay and health checks.

1|1|Updated Jun 28, 2025
Search Tags:#docker#containers#playwright#test-automation#health-checks
One-click install
npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill restart-test-containers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: restart-test-containers
Source: https://github.com/DarkMonkDev/WitchCityRope/tree/main/.claude/skills/restart-test-containers
Command: npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill restart-test-containers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, docker-compose.

What problem does it solve?

Ensures test containers are restarted with proper isolation and a clean test overlay setup for reliable E2E testing.

Core Features & Use Cases

  • Test isolation: Uses -p witchcityrope-test to keep test containers isolated from dev.
  • Overlay control: Builds and starts with docker-compose.test.yml by default.
  • Flexible rebuilds: Supports --skip-rebuild and --use-cache for speed.

Quick Start

From project root, run:

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

Frequently Asked Questions about restart-test-containers

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

FAQPage Schema
How do I restart Docker containers for E2E testing without affecting development?▼

Restart test containers using docker-compose with project isolation (-p witchcityrope-test) and a test overlay to keep test and dev environments separate. Run the Skill before E2E tests, after code changes, or when tests fail health checks to ensure a clean, isolated test setup.

When should I restart test containers during development?▼

Restart test containers before E2E tests, when existing tests are unhealthy or stopped, after code changes requiring a fresh image, or when the test database needs to reset. This prevents cross-environment contamination and ensures reliable test isolation.

Can I skip rebuilding Docker images when restarting test containers?▼

Yes, use the --skip-rebuild flag to restart containers without rebuilding images, or --use-cache to reuse cached layers. These options speed up restarts when you only need to clear state without pulling fresh code.

How does docker-compose test overlay isolation work for containers?▼

A test overlay (docker-compose.test.yml) applies test-specific configuration on top of your base compose file. Combined with project isolation (-p witchcityrope-test), it ensures test containers run independently with their own network, volumes, and services, preventing data bleed into development.

What health checks verify when test containers restart?▼

After restart, health checks verify the Web, API, Database, and Test Runner containers are ready. This confirms all services started correctly and are accepting traffic before E2E tests begin.

Do I need docker-compose to use this container restart approach?▼

Yes, this Skill requires docker and docker-compose. It uses docker-compose commands with overlay configuration and project flags to orchestrate isolated test container restarts with proper health verification.

Related Skills

Explore More Software Engineering Skills→
TheBushidoCollectiveTheBushidoCollective
187

docker-compose-basics

Creates and runs multi-container Docker apps with Compose.

Official
Basic
GYF0311GYF0311
5

smoke-test

Run post-restart smoke tests for gbrain and OpenClaw health with auto-fixes.

Community
Intermediate
alangebalangeb

docker

Manage Docker container lifecycles and service orchestration via compose operations.

Community
Intermediate
saintgo7saintgo7

k8s-pod-autostart

Configure s6-overlay hooks and .bashrc autostart to restore services in Kubernetes pods.

Community
Intermediate