env-teardown

Stop Docker containers, remove volumes, and purge local images.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill env-teardown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-teardown
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-ops/skills/mj-env-teardown
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill env-teardown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides a guided, multi-level approach to cleaning Docker environments, preventing accidental data loss and ensuring a clean slate for development or deployment.

Core Features & Use Cases

  • Graduated Cleanup: Offers three distinct levels of cleanup: stopping services, removing data volumes, and a full system reset including local images.
  • Safety Confirmation: Implements crucial confirmation steps for destructive operations (Level 2 and 3) to prevent irreversible data loss.
  • Use Case: After significant database schema changes, a developer needs to reset their local development environment completely. This skill guides them through the process, ensuring all old data and containers are removed before a fresh setup.

Quick Start

Use the env-teardown skill to perform a level 2 cleanup of the Docker environment.

Frequently Asked Questions about env-teardown

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

FAQPage Schema
How do I safely reset my Docker development environment without losing important data?

You can safely reset a Docker environment using a tiered cleanup process with safety confirmations. It manages container stopping, volume removal, and local image purging, requiring explicit confirmation before executing destructive operations to prevent irreversible data loss.

What is the best way to remove Docker Compose volumes and containers after schema changes?

The best way to remove Docker Compose volumes and containers is using a graduated cleanup skill. It offers three levels of environment reset including stopping services and removing data volumes, ensuring old containers are cleared for fresh setups.

Do I need Docker Desktop and a docker-compose.yml file to clean up my local environment?

Yes, you need Docker Desktop and a docker-compose.yml file in the current worktree to clean up your local environment. These prerequisites allow the tiered cleanup process to correctly identify and manage project containers and volumes.

Can I just stop Docker containers without deleting local images and volumes?

Yes, you can stop Docker containers without deleting local images and volumes. The tiered cleanup process features a graduated approach where Level 1 stops services, while Level 2 and 3 handle volume removal and local image purging.

Why does the Docker environment cleanup ask for confirmation before removing data volumes?

The Docker environment cleanup asks for confirmation before removing data volumes to prevent irreversible data loss. Destructive operations like volume removal and full system resets require explicit confirmation to protect local development data.