devcontainer-for-testing

Provision disposable devcontainers for Unix-side debugging and testing in /workspace.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/PeteJohn6/dotfile --skill devcontainer-for-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devcontainer-for-testing
Source: https://github.com/PeteJohn6/dotfile/tree/main/.agents/skills/devcontainer-for-testing
Command: npx skills add https://github.com/PeteJohn6/dotfile --skill devcontainer-for-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When Unix-side debugging or testing is needed, use the repository's test devcontainer defined at test/devcontainer/devcontainer.json as the default disposable environment. Manage its lifecycle through the devcontainer CLI rather than using ad hoc Docker commands. The container's /workspace contains the full source code. Operations inside /workspace do not need to worry about polluting the source code.

Core Features & Use Cases

  • Start and manage a disposable containerized workspace for Unix-based debugging, builds, and tests.
  • Operate inside /workspace to run, iterate, and validate changes without touching the host system.
  • Execute commands inside the running container with devcontainer exec for deterministic workflows and reproducible results.
  • Synchronize host changes into the container workspace when needed via the provided scripts, preserving a clean host environment.

Quick Start

Start the disposable test environment with the devcontainer CLI using the manifest at test/devcontainer/devcontainer.json.

Frequently Asked Questions about devcontainer-for-testing

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

FAQPage Schema
How do I run Unix tests in a disposable devcontainer without affecting my host system?

A disposable devcontainer isolates Unix debugging and testing by provisioning a containerized /workspace directory via the devcontainer CLI, keeping all build and test operations separate from the host system.

What is the best way to manage a disposable containerized workspace for Unix-side debugging?

Managing a disposable containerized workspace via the devcontainer CLI with test/devcontainer/devcontainer.json provides deterministic lifecycle control, replacing ad hoc Docker commands for reproducible Unix debugging.

How do I synchronize host changes into a running devcontainer workspace?

Execute the provided init-workspace.sh script to synchronize host changes into the running devcontainer's /workspace directory, preserving a clean host environment while updating the containerized source code.

Does the devcontainer CLI support executing commands inside a running test container?

Yes, the devcontainer CLI supports executing commands inside a running disposable test container using devcontainer exec, enabling deterministic workflows and reproducible test results within the /workspace directory.

Can I run builds and tests in an isolated workspace without modifying the host source code?

Yes, running builds and tests inside the devcontainer's isolated /workspace directory allows you to iterate and validate changes without modifying or polluting the host source code.

Why should I use a disposable devcontainer instead of ad hoc Docker commands for testing?

Using a disposable devcontainer instead of ad hoc Docker commands standardizes the container lifecycle through a devcontainer.json manifest, ensuring reproducible Unix test environments and clean host isolation.