config-schema-migrator

Backward-compatible schema evolution adds optional fields with defaults to existing Pydantic models, preserving old configs. This Skill automates the process by generating migration scripts that safely update schemas while maintaining type safety and allowing gradual user adoption of new structure.

Yes, automated migration scripts update existing config files to match evolved schemas. This Skill generates those scripts to handle field additions, type changes, and section restructuring, eliminating manual user edits while providing clear migration guidance and error messages.

Environment variable substitution injects secrets and dynamic values into configs using ${VAR} syntax. This Skill enforces type safety through Pydantic validators, supports variable expansion, and provides actionable error messages when substitution fails or values are missing.

Restructuring with backward compatibility uses Pydantic validators and discriminated unions to handle old and new schema layouts simultaneously. This Skill provides patterns for moving data between sections, applying type discrimination, and emitting deprecation warnings so users migrate at their own pace.

Testing migrations validates that automated scripts transform old configs to new schemas without data loss or type errors. This Skill integrates Pydantic's type enforcement with comprehensive error messaging to catch migration issues before users encounter them.

Type discriminators add flexibility when config components have different types and fields—like CLI versus HTTP adapters. This approach improves type safety and readability; this Skill guides schema refactoring from simple lists to discriminated unions with full backward compatibility.