docker-destructive-guardrails
Use this skill before running, or recommending, any Docker command that deletes, wipes, resets, or otherwise irreversibly changes state — even if the user just says to "clean up", "clear the cache", "start fresh", "wipe everything", "nuke it", "reset", "force remove", or "tear down" Docker resources. Covers generic Docker CLI destructive operations not owned by a more specific skill — docker rm, docker rm -f, docker container prune, docker kill, docker system prune, docker rmi/docker image rm, docker image prune -a, docker network rm, docker network prune, docker builder prune, docker buildx rm, docker context rm, and standalone (non-Compose) docker volume rm/docker volume prune. Also indexes destructive commands owned by other Docker skills (Compose, sandbox, Desktop). Core rule — state exactly what will be lost and get explicit confirmation first, except narrow, low-friction Tier 1 container cleanup.
- License
- Apache-2.0
- Compatibility
- Applies to any Docker CLI version. This is a behavioral guardrail skill, not a Dockerfile or Compose authoring skill.
Pinned to revision 4e8964e24a5a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/docker-destructive-guardrails/SKILL.md
- skills/docker-destructive-guardrails/checks/verification.md
- skills/docker-destructive-guardrails/references/cross-skill-destructive-command-index.md
- skills/docker-destructive-guardrails/references/docker-cli-destructive-commands.md
- skills/docker-destructive-guardrails/skill.yaml
Every link opens the file at its source, pinned to the revision this page describes.