dev-container-maintenance

Audit and update dev container configuration to match the regular development setup.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/TomekNocon/open-logistico --skill dev-container-maintenance-tomeknocon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-container-maintenance
Source: https://github.com/TomekNocon/open-logistico/tree/main/.ai/skills/dev-container-maintenance
Command: npx skills add https://github.com/TomekNocon/open-logistico --skill dev-container-maintenance-tomeknocon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Keeps the VS Code Dev Container and related setup in sync with the project's evolving development requirements to prevent drift between host and container environments.

Core Features & Use Cases

  • Audits regular development setup against the dev container to ensure parity of Node, Docker, and environment configurations.
  • Updates the .devcontainer file map, scripts, and volume definitions; refreshes docs and SPEC references accordingly.
  • Provides a guided workflow for maintenance, troubleshooting, and audit-compliant updates across the project.

Quick Start

Execute the dev container maintenance workflow to audit drift, apply updates to .devcontainer, and refresh environment configuration.

Frequently Asked Questions about dev-container-maintenance

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

FAQPage Schema
How do I fix dev container drift from my local development environment?

To fix dev container drift, you audit the regular development setup against the dev container configuration to identify mismatches in Node, Docker, and environment settings, then apply changes to the .devcontainer files and scripts to restore parity.

Why does my VS Code dev container have different Node or Docker configurations than my host?

Dev container configuration drift happens when project requirements evolve but the .devcontainer file map and volume definitions are not updated, causing mismatches between host and container environments across builds and startups.

Do I need to update documentation when maintaining my devcontainer setup?

Yes, dev container maintenance requires updating audit logs, troubleshooting references, and the SPEC-050-2026-02-26-dev-container-setup.md specification file to reflect any applied environment configuration changes and trigger a re-audit.

What's the best way to keep Docker dev container workspaces reproducible across builds?

The best way to keep dev container workspaces reproducible is to run a guided maintenance workflow that audits environment parity, applies updates to the .devcontainer file map, and refreshes documentation to prevent configuration drift.