Add Static Analysis Report

VerifiedSafe

Register an existing static-analysis report with the local review pipeline.

Sby Skills Guide Bot
DevelopmentIntermediate
007/24/2026
Claude Code
#static-analysis#code-review#cppcheck#flawfinder#automation

Recommended for

Our review

Registers an existing static-analysis report with the local review pipeline.

Strengths

  • Integrates multiple static analysis tools (cppcheck, flawfinder, coverity, etc.)
  • Automatically configures the review pipeline via a YAML config file
  • Preserves existing configurations while adding new reports

Limitations

  • Only works with the listed tools (no custom tool support)
  • The report must already be generated before calling this command
  • Requires the code-review-assistant plugin to be installed
When to use it

When you have already generated a static analysis report and want to incorporate it into an automated review pipeline.

When not to use it

If you prefer to run the static analysis directly from the review pipeline rather than importing a pre-existing report.

Security analysis

Safe
Quality score88/100

The skill runs a Python script with user-provided arguments to register static analysis reports. No destructive commands, network exfiltration, or obfuscation are present. The Bash usage is limited to a single controlled invocation.

No concerns found

Examples

Add cppcheck report
Add the cppcheck report at 'reports/cppcheck.xml' to the review config with project root 'sample_project'.
Add flawfinder with evidence
Add the flawfinder report 'flawfinder_results.xml' with additional evidence files (manifest, detailed, high-risk) to the review config for project 'myproject'.

description: Add an already generated static-analysis report to a review config. argument-hint: "<tool> <report-path> [--project-root <path>] [--output-dir <path>] [--config <path>]" arguments:

  • add_args allowed-tools:
  • Bash
  • Read
  • Glob user-invocable: true disable-model-invocation: false

Add Report

Register an existing static-analysis report with the local review pipeline.

Supported tools:

  • cppcheck
  • flawfinder
  • splint
  • cppdepend
  • coverity

Run from the repository root:

python "${CLAUDE_PLUGIN_ROOT}/plugins/code-review-assistant/scripts/review.py" /code-review-assistant:add <tool> <report-path> [options]

If the wrapper path above does not exist, fall back to:

python "${CLAUDE_PLUGIN_ROOT}/scripts/review.py" /code-review-assistant:add <tool> <report-path> [options]

Common usage:

python plugins/code-review-assistant/scripts/review.py /code-review-assistant:add cppcheck reports/cppcheck.xml --project-root sample_project

Behavior:

  1. Copy the report into <output-dir>/raw-reports/<tool>/.
  2. Create or update review.auto.yaml.
  3. Enable the selected tool in the config with mode: import.
  4. Preserve existing enabled tools in the config.
  5. Validate the generated config.

Options:

  • --config <path> updates an existing config.
  • --project-root <path> is required when creating a new config.
  • --output-dir <path> controls where the copied report and generated config are written.
  • --provider heuristic|codex|claude_code sets or updates hosted/local review mode.
  • --evidence-artifact <path> copies extra evidence beside the report; useful for flawfinder manifest/detailed/high-risk files.

After adding reports, run:

python plugins/code-review-assistant/scripts/review.py all --config <output-dir>/review.auto.yaml
Related skills