Static Analysis

Applicable Scenarios

• Need to perform static analysis on code before submission to detect potential defects.
• Industries such as automotive and medical require MISRA-C 2012 compliance checks.
• Need to use cppcheck, clang-tidy, or GCC

  -fanalyzer

  for code quality reviews.
• Need to view summaries of static analysis results grouped by severity level.

Necessary Inputs

• Source code directory path.
• At least one available static analysis tool (cppcheck, clang-tidy, or GCC 12+).
• Optional

  compile_commands.json

  path (improves clang-tidy accuracy).
• Optional severity level filtering and MISRA check toggle.

Auto Detection

• The

  --detect

  mode detects the availability and versions of cppcheck, clang-tidy, and arm-none-eabi-gcc.
• GCC

  -fanalyzer

  requires GCC 12+, and the script will check the version number.
• Automatically searches for

  compile_commands.json

  in the workspace.

Execution Steps

1. First read references/usage.md to confirm which analysis tool to use this time.
2. If unsure whether the tool is available, first run the

   --detect

   mode of scripts/static_analyzer.py.
3. Run cppcheck analysis with

   --cppcheck --source <dir>

   .
4. Run clang-tidy analysis with

   --clang-tidy --source <dir>

   .
5. Run GCC analyzer analysis with

   --gcc-analyzer --source <files>

   .
6. When MISRA compliance is required, add the

   --misra

   parameter to enable the cppcheck MISRA addon.
7. Read references/misra-quick-ref.md to learn about common MISRA violations.

Failure Handling

• Returns

  environment-missing

  when all analysis tools are unavailable.
• Returns

  artifact-missing

  when the specified source code directory does not exist.
• Returns

  project-config-error

  when

  compile_commands.json

  is specified but invalid.
• Returns

  target-response-abnormal

  when the analysis tool exits abnormally.

Platform Notes

• cppcheck and clang-tidy are available on all three major platforms and can be installed via package managers.
• GCC

  -fanalyzer

  requires GCC 12+, and embedded cross-compiler versions may be lower.
• The built-in script uses Python standard libraries and subprocess, making it cross-platform compatible.

Output Conventions

• Output findings grouped by severity level (error, warning, style, information).
• Each finding includes file path, line number, rule ID, and description.
• The

  --summary

  mode only outputs statistical figures.
• MISRA mode additionally outputs the violated rule numbers.

Handover Relationships

• When critical defects are found and require fixes before rebuilding, hand over to the corresponding

  build-*

  skill.
• When needing to understand the memory impact of the code, hand over to

  memory-analysis

  .