devcontainer-merger

Merge per-service devcontainer.json configurations into a single root DevContainer.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill devcontainer-merger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devcontainer-merger
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/devcontainer-merger
Command: npx skills add https://github.com/joleques/northstar-ai --skill devcontainer-merger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes services inside a bounded context and consolidates individual DevContainer configurations into a single Root DevContainer at the workspace root, delivering a lean, unified development environment.

Core Features & Use Cases

  • Fail-fast validation: detects any individual devcontainer configuration and aborts if none exist.
  • Requirements analysis: reads devcontainer.json to identify languages/SDKs and required infrastructure, and only considers infra declared in the devcontainer configuration.
  • Unification strategy: merges into a lean root DevContainer by selecting a primary stack image and constructing a custom Dockerfile to include secondary dependencies.
  • Infrastructure discipline: includes only declared infrastructure services in the root docker-compose.yml, ignoring unrelated root files.
  • Root DevContainer generation: creates .devcontainer/ with devcontainer.json, Dockerfile, and docker-compose.yml configured to mount the workspace and extensions.
  • Documentation: writes a brief README or comment noting success and included SDKs and infra.

Quick Start

Trigger the /init-bounded-context workflow to generate a unified root DevContainer.

Frequently Asked Questions about devcontainer-merger

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

FAQPage Schema
How do I merge multiple devcontainer configurations into a single workspace?

You can merge devcontainer configurations by triggering the init-bounded-context workflow, which analyzes per-service devcontainer.json files and consolidates them into a single root DevContainer.

What happens if there are no individual devcontainer.json files in my services?

The process uses a fail-fast validation approach that aborts if no individual devcontainer configurations are detected, ensuring it only runs when service-level devcontainer.json files exist.

How does a unified root DevContainer handle multiple SDKs and languages?

A unified root DevContainer selects a primary stack image and constructs a custom Dockerfile to include secondary dependencies, ensuring all required SDKs identified from devcontainer.json are available.

Does the root DevContainer include all services from docker-compose.yml?

No, the root DevContainer includes only infrastructure services explicitly declared in the devcontainer configurations, ignoring unrelated root files to maintain infrastructure discipline.

Can I use this to unify devcontainers for a bounded context with different infrastructure requirements?

Yes, it reads devcontainer.json to identify required infrastructure within bounded contexts and generates a root docker-compose.yml that mounts the workspace while only including declared infra services.

What files are generated when consolidating per-service devcontainers?

Consolidating per-service devcontainers generates a .devcontainer directory containing a unified devcontainer.json, a custom Dockerfile for dependencies, and a docker-compose.yml for declared infrastructure.