Migrate legacy devcontainer.json files to current schema standards.
npx skills add https://github.com/notwillk/skills --skill modernize-devcontainer
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
Migrate and update legacy devcontainer configurations to current standards, addressing schema evolution and deprecated properties to ensure future compatibility.
To modernize a legacy devcontainer, review the existing devcontainer.json, apply the migration steps, and validate the updated configuration.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
anthrilAudit GTM containers and generate a GA4 baseline change plan.
NicoVIIIGenerate devcontainer configurations that pin tool versions and integrate with GitHub Actions.
dereknguyen269Detect, validate, and generate JSON-LD Schema.org structured data for page URLs.
Snowflake-LabsApply regex migration rules to SQL files with AI-suggested edits.
