메뉴
Fixes or justifies Polyspace findings after analysis. Use when the user asks to "fix this finding", "fix these defects", "fix violations", "address Polyspace results", or wants to resolve static analysis findings.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Sets up the Polyspace Agentic Toolkit for any supported AI agent. Use when the user asks to "set up Polyspace", "set up the Polyspace Agentic Toolkit", "install the Polyspace MCP Server", "configure Polyspace for my agent", or wants to get Polyspace working with their AI application.
Creates Polyspace build options files from build commands or compilation databases. Use when the user asks to "configure build options", "create build options file", "set up Polyspace build", or needs to configure compiler settings for Polyspace analysis.
Creates or modifies Polyspace checkers configuration files. Use when the user asks to "configure checkers", "set up MISRA checking", "enable CWE", "create checkers file", or needs to select coding standards for Polyspace analysis.
Provides Polyspace documentation entry points and links. Use when the user asks about "Polyspace documentation", "where is the Polyspace docs", "documentation links", or needs to find general Polyspace documentation.
Finds documentation for Polyspace checkers and coding rules. Use when the user asks "what does this checker do", "find checker documentation", "explain this Polyspace rule", or wants to understand a specific Polyspace finding.
REQUIRED before searching for any Polyspace option documentation page. Use when the user asks about a Polyspace option (-c, -target, -sources, -boolean-types, -misra3, etc.), wants to find an option's doc page, or asks 'what does this option do'. This skill contains the only reliable method to locate option reference pages — URLs cannot be guessed from the flag name.
| name | fix-findings |
| description | Fixes or justifies Polyspace findings after analysis. Use when the user asks to "fix this finding", "fix these defects", "fix violations", "address Polyspace results", or wants to resolve static analysis findings. |
| license | MathWorks BSD-3-Clause |
| metadata | {"version":"1.0"} |
After running Polyspace as You Code analysis, use this workflow to address each finding.
Read the finding's family and acronym from the analysis results (e.g., Defect:INT_OVERFLOW, MISRA-C3:8.4).
Invoke the find-checker-documentation skill to get the documentation URL for the finding. Fetch the documentation page to understand what the checker detects and why.
Fix the code if the finding reveals a genuine issue:
run-analysis skill) to confirm the finding is resolved.Justify the finding if it is a false positive, intentional behavior, or prevented by external constraints:
justify-findings skill for annotation syntax and guidelines.Repeat steps 1-2 for each remaining finding.
Copyright 2026 The MathWorks, Inc.