SLCI Inspection Incompatibility Analysis

Analyze SLCI code inspection results and trace failures back to compatibility constraint violations or known limitations by matching failed code lines against known incorrect code generation patterns and documented limitation scenarios.

When to Use

• User asks why SLCI inspection failed or has verification errors
• User wants to trace inspection failures to their root-cause settings
• User has an inspection report with Failed/Error/Unverified items
• User asks to diagnose code inspection issues before re-running
• User wants to understand which compatibility settings caused inspection failure

When NOT to Use

• User wants to check model compatibility before running inspection (no inspection failure context), use slci-compatibility-analysis instead
• User confirms the inspection failure is not related to a compatibility issue
• User wants general Simulink model building or code generation help

Workflow

0. Clarify Intent

Ask the user whether the inspection failure might be related to a compatibility issue before taking any other action. Do not search for files or run MATLAB until the user confirms.

• Yes → proceed to Step 1.
• No → stop this skill.
• Unsure → explain what compatibility issues are and ask again.

1. Locate the Inspection Report

Get the report folder from MATLAB:

c = slci.Configuration('<model_name>');
reportFolder = c.getReportFolder();

Look for <model_name>_report.html (or .pdf/.doc). If found, compare the model's timestamp against the report's, warn if the report may be stale.

If the report does NOT exist, stop and warn the user. Suggest c.inspect(). If the user explicitly asks to run inspection, first check whether generated code is stale or missing and regenerate if needed before inspecting.