docker

Validate Docker context before commands and restore local defaults after remote operations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dewittn/dotfiles --skill docker-dewittn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker
Source: https://github.com/dewittn/dotfiles/tree/main/.claude/skills/docker
Command: npx skills add https://github.com/dewittn/dotfiles --skill docker-dewittn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Docker context safety and operational patterns. Consult before running Docker commands to ensure correct context (orbstack=local, coto-v3=remote).

Core Features & Use Cases

  • Read first: docs showing how to manage contexts.
  • Before any Docker command — verify current context matches the intended environment.
  • After remote operations — restore to orbstack.
  • Volume operations — prompt user before performing remote volume changes.
  • Starting local dev — run Docker with run_in_background: true.

Quick Start

Check that your Docker context matches your intended environment before executing commands.

Frequently Asked Questions about docker

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

FAQPage Schema
How do I prevent Docker commands from running in the wrong environment?

Docker command safety relies on pre-command context validation to ensure the active context matches the intended environment, preventing accidental cross-environment execution before operations begin.

What is a Docker context and how does it affect local versus remote operations?

A Docker context defines the target environment for commands, such as orbstack for local and coto-v3 for remote. Verifying the context prevents executing local commands on remote servers.

How do I restore a safe Docker context after finishing remote operations?

After completing remote operations, restore the Docker context to the local orbstack default. This automatic restoration prevents subsequent commands from unintentionally executing on the remote environment.

How do I safely perform Docker volume changes on a remote server?

Performing remote Docker volume changes requires explicit user confirmation before execution. This guardrail prompts the user to verify the operation, preventing accidental data loss.

What is the best way to start local Docker development without blocking the terminal?

Start local Docker development by running commands with run_in_background set to true. This allows the environment to initialize without blocking the terminal session.

Why does my Docker context switch unexpectedly between local and remote?

Docker context switches happen when operations alter the active environment. This Skill implements context validation and restores the safe orbstack default after remote tasks to prevent unexpected switches.