modernize-devcontainer

Name: modernize-devcontainer
Availability: InStock
Author: notwillk

Migrate legacy devcontainer.json files to current schema standards.

Updated Apr 25, 2026

Search Tags:#validation #migration #devcontainer #customizations #legacy-config #schema-upgrade #oci-features

Ready to run

npx skills add https://github.com/notwillk/skills --skill modernize-devcontainer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: modernize-devcontainer
Source: https://github.com/notwillk/skills/tree/main/skills/modernize-devcontainer
Command: npx skills add https://github.com/notwillk/skills --skill modernize-devcontainer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrate and update legacy devcontainer configurations to current standards, addressing schema evolution and deprecated properties to ensure future compatibility.

Core Features & Use Cases

Schema version upgrades
Deprecated property migrations (appPort to forwardPorts, extensions to customizations, settings to customizations)
Feature ID modernization to OCI-based formats
Validation and testing of updated configurations
Use Case: update an old devcontainer.json to align with the latest spec and verify a clean rebuild

Quick Start

To modernize a legacy devcontainer, review the existing devcontainer.json, apply the migration steps, and validate the updated configuration.

Frequently Asked Questions about modernize-devcontainer

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

FAQPage Schema

How do I migrate a legacy devcontainer.json to the current schema?▼

To migrate a legacy devcontainer.json, update deprecated properties like appPort to forwardPorts, move extensions and settings into customizations, and modernize feature IDs to OCI-based formats. Validate the JSON structure to ensure required fields exist for a clean rebuild.

What devcontainer properties are deprecated and need migration?▼

Deprecated devcontainer properties requiring migration include appPort, which moves to forwardPorts, and top-level extensions and settings, which are relocated into the customizations block. Feature IDs also require modernization to align with current OCI-based standards.

How do I update devcontainer feature IDs to OCI format?▼

Updating devcontainer feature IDs to OCI format involves replacing legacy feature identifiers with modern OCI-based references. This modernization step ensures compatibility with current devcontainer standards and OCI-based feature registries.

Does devcontainer migration validate the JSON structure and required fields?▼

Devcontainer migration validates the JSON structure and ensures required fields exist in the updated configuration. This validation process confirms the schema upgrade is structurally sound and compatible with OCI-based features before rebuilding.

What is the best way to upgrade an old devcontainer configuration schema?▼

The best way to upgrade an old devcontainer configuration schema is to apply targeted migrations for deprecated properties, modernize feature IDs to OCI formats, and validate the final JSON structure to guarantee compatibility with current standards.

Why do I need to move extensions and settings into customizations?▼

You need to move extensions and settings into customizations because the previous devcontainer properties are deprecated in current schema versions. Consolidating them into the customizations block ensures future compatibility and a successful schema upgrade.