docker-destructive-guardrails
Skill1 starsChanged 15 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- docker/skillsword for word, first seen Nov 13, 2026
Other versions1 project uses a version of this.
Word for word · 1
- docker/skills★ 635100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .claude/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Do not use this skill when:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Docker Destructive Command Guardrails
Overview
This skill provides the cross-product policy for handling destructive or irreversible Docker CLI operations: commands that delete data, remove resources, or otherwise cannot be undone. Use it whenever a task could reasonably lead to running one of these commands, even if the user never names the command directly. It covers the generic Docker CLI commands with no home in a more specific skill, and it indexes where other destructive commands (Compose, sandbox, Desktop) are documented.
When to use this skill
Activate this skill when:
- The user asks to "clean up", "clear the cache", "start fresh", "wipe everything", "nuke it", "reset", "force remove", or "tear down" Docker resources without naming a specific command
- The agent is considering
docker rm,docker rm -f,docker container prune,docker kill,docker stop,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, or standalone (non-Compose)docker volume rm/docker volume pruneas a fix for an unrelated problem (disk space, a stuck container, a stale network, a broken build cache, an old builder or volume) - The user wants a cross-product overview of destructive commands across Docker skills
Do not use this skill when
Do not use this skill when:
- The destructive command in question is Compose-specific (
docker compose down -v,docker compose rm -v,docker volume rm/docker volume prunein a Compose project) — usedocker-compose-patternsdirectly, which owns that guidance in full detail - The task is authoring or reviewing a Dockerfile or
compose.yamlwith no cleanup or deletion involved - The operation is non-Docker (git, filesystem, cloud resources) — this skill covers Docker CLI operations only
Core guidance
The core rule for every command below: state exactly what will be deleted, stopped, or lost, and get explicit confirmation from the user before running it. Never run a destructive command as a default troubleshooting or "just clean it up" reflex — disk space, stuck containers, and stale caches almost always have a narrower, non-destructive fix. See references/docker-cli-destructive-commands.md for exact flags and the safe, scoped alternative for each.
The container-lifecycle commands — docker rm, docker rm -f, docker container prune, and docker kill — don't all carry the same risk, so they're split into two tiers below instead of one flat rule. docker stop follows a related but distinct reversible-action rule right after the tiers. Every other command in this list follows the flat rule stated above with no exceptions: state what's lost, get explicit confirmation, and wait for the user's answer before running it.
Tier 1 — low-friction container cleanup
Applies only to docker rm <name> on an already-stopped container and docker rm -f <name> on a container the agent itself created and started earlier in the same session purely for testing or debugging — the -f carve-out applies even when the container is still running, since that's the only reason -f would be needed. All of the following must hold: the container is already stopped, or was created/started by the agent itself this session for testing/debugging; there's no known unpersisted state at risk; the action targets one specific, identified container rather than an unscoped sweep; and the agent is acting on an explicit user ask this session, not its own initiative. When every condition holds, the agent removes the container, states what it did, and proceeds — no blocking confirmation is required first. Tier 2's docker rm -f rule below applies to every other case.
Tier 2 — container commands needing confirmation
docker kill is always Tier 2 (see the reference for why no stopped-container exception exists for it). Also Tier 2: docker container prune (it always sweeps every stopped container on the host, never just the one the agent is cleaning up), docker rm -f on any container that doesn't meet every Tier 1 condition above (in particular, a running container the agent didn't create/start this session, or one it did but is acting on without an explicit user ask), any other unscoped sweep regardless of container state (e.g. docker rm -f $(docker ps -aq), "remove/kill all containers"), a container the agent didn't create and has no context on, and any action taken on the agent's own initiative rather than an explicit user ask. These carry the same confirmation bar as every flat-rule command in this skill: state exactly what will be lost and get explicit confirmation before running anything — no exception carved out.
docker stop — reversible, outside the tier model
docker stop doesn't remove anything — the container still exists and can be restarted with docker start — so it sits outside the Tier 1/Tier 2 removal model above. It's still in scope for this skill because it interrupts a running process (SIGTERM, then SIGKILL after the timeout) and discards any unpersisted in-container state. On the agent's own test/debug container from this session, treat it like Tier 1: stop it and state what happened, no blocking confirmation required. On any other container, state that it will stop running and any unsaved in-memory state will be lost, then get confirmation first.
docker system prune— deletes stopped containers, unused networks, dangling images, and build cache;-aalso deletes unused tagged images, and--volumesalso deletes unused anonymous volumes (named volumes are untouched — deleting those needs a separatedocker volume rm).docker rmi/docker image rm— deletes a specific image; see the reference for-f's exact (partly unverified) override behavior on multi-tag/referenced images.docker image prune -a— deletes every image not referenced by any container, running or stopped, not just dangling ones.docker network rm— deletes the specifically named network(s) passed as arguments; see the reference for how its-fflag differs fromdocker context rm -fbelow.docker network prune— deletes every custom network not attached to a container.docker builder prune— clears the BuildKit cache;-a/--allalso removes internal helper/frontend images and cache shared with other build outputs, forcing a cold rebuild for anyone using that cache.docker buildx rm— removes a builder instance, distinct from the cachedocker builder pruneclears — see the reference for flag details.docker context rm— deletes a context's local connection config; doesn't affect remote resources but may not be trivially reconstructable. Unlikedocker network rm -fabove,docker context rm -fgenuinely forces removal even if the context is currently in use.docker volume rm/docker volume prune(standalone, no Compose project in play) — deletes volume data directly and irreversibly;docker volume prune -a/--allwidens the default anonymous-only scope to named volumes too. For a Compose project's own volumes, usedocker-compose-patternsinstead (see Related skills); for a volume declaredexternal: truein a compose.yaml but not managed by that Compose project, this skill's guidance applies since Compose won't touch it viadown -v.
Related skills
- For Compose-specific destructive commands (
docker compose down -v,docker compose rm -v,docker volume rm/docker volume prunein a Compose context), usedocker-compose-patterns— it owns that guidance in full detail; this skill only indexes it. This skill owns the standalone (non-Compose) case fordocker volume rm/docker volume pruneitself — see Core guidance andreferences/docker-cli-destructive-commands.md. - For Dockerfile internals, build caching, and image size optimization (non-destructive concerns), use
docker-build-strategies. - For first-time Docker project scaffolding, use
docker-project-foundations. - For sandbox (sbx) destructive commands (
sbx rm,sbx prune), usedocker-sandboxes-lifecycle— it owns that guidance in full detail; this skill only indexes it. Docker Desktop destructive-command guardrails will live in their own skill once merged (seereferences/cross-skill-destructive-command-index.mdfor tracking status); do not assume their content until that skill ships.
References
references/docker-cli-destructive-commands.md— Per-command breakdown of exact flags, what's deleted, and the safe/scoped alternative for each generic Docker CLI destructive command.references/cross-skill-destructive-command-index.md— Cross-product table of destructive commands across all Docker skills, including a pending placeholder for Docker Desktop.
Assets
This skill has no bundled assets.
Checks
checks/verification.md— Manual review runbook, including example bad/good dialogues for handling destructive-command requests.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

