What problem does it solve?
When upgrading MATLAB releases, scripts that programmatically set preferences via .PersonalValue or .TemporaryValue break because setting paths get renamed, moved, retyped, or removed. Manually diffing factory settings between releases and fixing every startup script, team preference file, or test setup script is slow and error-prone.
Core Features & Use Cases
- Cross-release settings diff: Compares factory settings between two MATLAB installations using
.hpp source files or strings extraction from compiled DLL/SO binaries to build a rename/move/remove/added change map.
- Automatic script rewriting: Parses any
.m file that assigns MATLAB settings, verifies each setting against the target release, translates values when types change (e.g., logical to string enum), and writes a new release-suffixed file without touching the original.
- Runtime validation: Runs the migrated file in the target MATLAB to confirm zero errors, fixing moved paths and type mismatches iteratively.
- Use Case: After installing R2026a, point the skill at your existing
startup.m written for R2025b and receive a validated startup_R2026a.m with updated paths, translated values, and a migration summary.
Quick Start
Migrate my startup.m settings script from R2025b to the latest installed MATLAB release and validate the result.