What problem does it solve? Developers in this repository run commands in the wrong environment or hit opaque failures: containers built from stale definitions, ports published on the wrong service, worktrees colliding over port ranges, and commits rejected by lint-staged in linked worktrees. This Skill defines exactly where each command runs and how to recover from each named failure. ## Core Features & Use Cases - Command routing: package, build, test, lint, and database commands run via devcontainer exec --workspace-folder ., while git and gh run on the host. - Container lifecycle management: start with devcontainer up, and recreate with --remove-existing-container whenever .devcontainer/ changes or port bindings go stale. - Per-worktree port allocation: initialize.sh derives a host port base from DEV_ENV_PORT, CONDUCTOR_PORT, or a workspace path hash so multiple worktrees run concurrently. - Failure diagnosis: covers EAI_AGAIN on registry requests, "port is already published by", ports that answer nothing, and lint-staged stash failures in linked worktrees. - Use Case: A published port answers nothing after you edited the compose file — the Skill explains that Docker fixes bindings at container creation and tells you to recreate with --remove-existing-container. ## Quick Start Ask the assistant to run the test suite for this repository and it will execute it inside the devcontainer using devcontainer exec.
