matlab-review-codelisted

# Code Review Systematically review MATLAB code for quality, correctness, performance, and adherence to MathWorks coding conventions using static analysis and manual inspection patterns. ## When to Use - User asks to review, audit, or improve code quality - User wants to check adherence to MathWorks coding standards - Preparing code for handoff, publication, or open-source release - After a significant implementation — verify before committing - User reports "code smells" or asks for cleanup suggestions ## When NOT to Use - User wants to debug a runtime error — use `matlab-debugging` instead - User wants to optimize performance — use performance profiling skills - User wants to generate tests — use `matlab-testing` instead ## Workflow 1. **Run static analysis** — Use `check_matlab_code` MCP tool on all target files 2. **Load coding standards** — Read the `matlab_coding_guidelines` MCP resource 3. **Check naming** — Verify functions, classes, variables, and files follow conventions 4. **Review function signatures** — Arguments blocks, input/output counts, name-value patterns 5. **Assess structure** — Function length, nesting depth, complexity 6. **Check patterns** — Vectorization, preallocation, modern API usage 7. **Summarize** — Report findings by severity: errors > warnings > suggestions ## Step 1: Static Analysis Use the `check_matlab_code` MCP tool on each file. Then inspect results programmatically: ```matlab info = checkcode("src/computeArea.m", "-struct"); fo