matlab-modernize-code
Skill8 starsChanged 5 months agoMITView on GitHub
Modernize deprecated MATLAB functions and patterns. Use when check_matlab_code or checkcode reports "not recommended" or "to be removed" warnings, when migrating legacy code, or when replacing deprecated APIs (trainNetwork, csvread, xlsread, datenum, eval, subplot, guide, optimset, wavread, svmtrain, uicontrol) with current equivalents.
In this repository58 other files it gives its agents.
- skills/writing-polish/humanizer/AGENTS.mdAGENTS.md
- frontend-designSkill
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- github-codex-keySkill
- github-ssh-key-pushSkill
- implementSkill
- improve-codebase-architectureSkill
- prototypeSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- huggingface-accelerateSkill
- quantizing-models-bitsandbytesSkill
- gpuboxSkill
- evaluating-llms-harnessSkill
- ml-training-recipesSkill
- peft-fine-tuningSkill
- experiment-tracking-swanlabSkill
- unslothSkill
- matlab-add-awgnSkill
- matlab-agentic-toolkit-setupSkill
- matlab-build-appSkill
- matlab-create-live-scriptSkill
- matlab-debuggingSkill
- matlab-design-digital-filterSkill
- matlab-display-imageSkill
- matlab-install-productsSkill
- matlab-list-productsSkill
- matlab-map-database-objectsSkill
- matlab-model-serdes-systemsSkill
- matlab-read-databaseSkill
- matlab-review-codeSkill
- matlab-testingSkill
- matlab-use-duckdbSkill
- matlab-write-databaseSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- teachSkill
- writing-great-skillsSkill
- ara-compilerSkill
- ara-research-managerSkill
- research-paper-notesSkill
- ara-rigor-reviewerSkill
- brainstorming-research-ideasSkill
- creative-thinking-for-researchSkill
- academic-plottingSkill
- ml-paper-writingSkill
- paper-spineSkill
- humanizerSkill
- prompt-optimizerSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
After static analysis reveals deprecated API usage
- Distinctive: line 57
Never use these in new code:
- Distinctive: line 72
Prefer these in all new code:
- Very specific: line 177
Always run check_matlab_code first — let static analysis find deprecated usage
- Distinctive: line 180
When writing new code, use the modern pattern from the start — don't write deprecated code and fix it later
- Distinctive: line 182
When migrating, test the modern replacement against the old behavior to confirm equivalence
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Modernization
Replace deprecated MATLAB functions and anti-patterns with modern equivalents. This skill is the resolver — check_matlab_code is the detector.
When to Use
check_matlab_codeorcheckcodereturns "not recommended" or "to be removed" warnings- User asks to modernize, migrate, or update old MATLAB code
- Code uses functions listed in the quick reference table below
- After static analysis reveals deprecated API usage
- Writing new code in a domain that has known deprecated patterns
When NOT to Use
- Reviewing code quality broadly — use
matlab-review-code(which may then trigger this skill) - Debugging runtime errors — use
matlab-debugging - Performance profiling — use performance skills (though anti-patterns below overlap)
Quick Reference: Top Deprecated Functions
| Deprecated | Use instead | Since | Category |
csvread / dlmread | readmatrix | R2019a | File I/O |
csvwrite / dlmwrite | writematrix | R2019a | File I/O |
xlsread | readtable, readmatrix | R2019a | File I/O |
xlswrite | writetable, writematrix | R2019a | File I/O |
datenum / datestr | datetime | R2014b | Date/Time |
subplot | tiledlayout / nexttile | R2019b | Graphics |
eval / evalc / evalin | Dynamic field names, function handles | — | Security |
str2num | str2double | — | Security |
trainNetwork | trainnet | R2024a | Deep Learning |
LayerGraph / SeriesNetwork | dlnetwork | R2024a | Deep Learning |
classify (DL) | minibatchpredict + scores2label | R2024a | Deep Learning |
uicontrol | uibutton, uidropdown, etc. | R2016a | UI/App |
guide | appdesigner | R2025a | UI (Removed) |
optimset | optimoptions | R2013a | Optimization |
strmatch | startsWith, matches | R2019b | Strings |
clear all | clearvars | — | Performance |
Critical Anti-Patterns
Never use these in new code:
| Anti-pattern | Problem | Use instead |
eval / evalc / evalin | Security risk, prevents JIT optimization, difficult to debug | Dynamic field names s.(name), function handles |
str2num | Uses eval internally — code injection risk | str2double |
| Growing arrays in loops | O(n²) memory reallocation | Preallocate with zeros, cell |
global variables | Hidden state, performance penalty | Pass as arguments or use structs |
clear all | Removes functions from memory, forces recompilation | clearvars |
cd during execution | Forces function re-resolution | fullfile for paths |
exist('var','var') in loops | Expensive state query | Initialize variable before loop |
| Large data in code | Slow parsing, hard to maintain | Save to .mat or .csv files |
Modern Design Patterns
Prefer these in all new code:
Table-Based Workflows
data = readtable('sensors.csv');
data.Timestamp = datetime(data.Timestamp);
data.Status = categorical(data.Status);
recentData = data(data.Timestamp > datetime('today') - days(7), :);
summary = groupsummary(recentData, 'SensorID', 'mean', 'Value');String Arrays (not char arrays)
name = "John"; % not 'John'
names = ["John", "Jane", "Bob"]; % not {'John','Jane','Bob'}
fullName = firstName + " " + lastName; % not [first,' ',last]
idx = contains(names, "Jo"); % not cellfun + strfindArguments Block (not nargin/varargin)
function result = processData(data, options)
arguments
data (:,:) double
options.Method (1,1) string {mustBeMember(options.Method, ["fast","accurate"])} = "fast"
options.Verbose (1,1) logical = false
end
endVectorization (not loops)
% Instead of: for i=1:n, V(i) = pi/12*(D(i)^2)*H(i); end
V = pi/12 * (D.^2) .* H;
% Instead of: loop with if
Vgood = V(D >= 0); % logical indexingPreallocation
result = zeros(1, n); % numeric
C = cell(1, n); % cell array
S(n) = struct('f1', []); % struct arrayKey Migrations
File I/O: csvread/xlsread → readmatrix/readtable
% Old → Modern
M = csvread('data.csv'); % M = readmatrix('data.csv');
M = dlmread('data.txt','\t'); % M = readmatrix('data.txt','Delimiter','\t');
[n,t,r] = xlsread('f.xlsx'); % T = readtable('f.xlsx');
csvwrite('out.csv', M); % writematrix(M, 'out.csv');
xlswrite('out.xlsx', data); % writetable(T, 'out.xlsx');Deep Learning: trainNetwork → trainnet
% Old: classificationLayer specifies loss implicitly
net = trainNetwork(X, Y, layers, options);
% Modern: specify loss explicitly, no classificationLayer needed
net = trainnet(X, Y, layers, "crossentropy", options);
% Prediction
scores = minibatchpredict(net, XTest);
YPred = scores2label(scores, classNames);eval → Dynamic Field Names / Function Handles
% Old: eval([varName ' = 42;']);
s.(varName) = 42;
% Old: result = eval(['process_' method '(x)']);
handlers.fast = @processFast;
handlers.slow = @processSlow;
result = handlers.(method)(x);References
Load these when working in a specific domain:
| Load when... | Reference |
| Deprecated core MATLAB functions (file I/O, strings, deep learning, UI) | reference/core-functions-guidance.md |
| Performance anti-patterns, vectorization, preallocation | reference/performance-guidance.md |
| Signal processing deprecated functions | reference/signal-processing-guidance.md |
| Audio/video I/O migration (wavread, aviread) | reference/audio-video-guidance.md |
| Optimization toolbox (optimset, optimtool) | reference/optimization-guidance.md |
| Control systems plot options | reference/control-systems-guidance.md |
| Image processing ROI objects | reference/image-processing-guidance.md |
| Statistics/ML (svmtrain, dataset, classregtree) | reference/statistics-ml-guidance.md |
| Simulink configuration and blocks | reference/simulink-guidance.md |
| Functions completely removed (guide, optimtool, fints, wavread) | reference/removed-functions-guidance.md |
| Communications System objects | reference/communications-guidance.md |
Conventions
- Always run
check_matlab_codefirst — let static analysis find deprecated usage - After checkcode, scan the source for patterns checkcode misses:
subplot(not flagged),str2num(sometimes not flagged),globalvariables, growing arrays may only warn about size change - Fix deprecated patterns before other code quality issues
- When writing new code, use the modern pattern from the start — don't write deprecated code and fix it later
- For functions marked "Removed" — they will cause immediate errors, not just warnings
- When migrating, test the modern replacement against the old behavior to confirm equivalence
- Consult the domain-specific reference file for detailed migration patterns with code examples
Copyright 2026 The MathWorks, Inc.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

