matlab-review-code

To review MATLAB code for quality, run automated static analysis to surface warnings and errors, then validate naming conventions, function signatures, and structural complexity against MathWorks coding guidelines to ensure maintainability.

Static analysis for MATLAB code evaluates source files without execution to detect coding smells, risky patterns like eval, and standard violations. You need it before code publication, handoff, or pre-commit verification to prevent bugs and performance regressions.

To check MATLAB code for risky patterns like eval before handoff, use static analysis to flag high-risk constructs and legacy constructs, prioritizing findings by severity from errors to warnings and suggestions for a practical cleanup report.

Yes, you can automatically detect legacy MATLAB patterns and code smells by running static analysis across project folders to check for modern vs. legacy constructs like datetime and tiledlayout, ensuring public APIs use arguments blocks.

MATLAB code review supports severity-based reporting by prioritizing findings from errors to warnings and then suggestions, producing a practical summary suitable for code cleanup, publication readiness, and development audits.

Automated MATLAB static analysis focuses on structural complexity, naming conventions, and known risky patterns but requires the check_matlab_code tool and matlab_coding_guidelines reference to function, limiting its scope to predefined coding standards.