Add Static Analysis Report

VerifiedSafe

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

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

Recommended for

Automated summary

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

How this analysis is made

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/add-static-analysis-report-mryiqgvh/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/add-static-analysis-report-mryiqgvh' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/add-static-analysis-report-mryiqgvh/download' --output '.skill-downloads/add-static-analysis-report-mryiqgvh/SKILL.md.part' && mv '.skill-downloads/add-static-analysis-report-mryiqgvh/SKILL.md.part' '.skill-downloads/add-static-analysis-report-mryiqgvh/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/add-static-analysis-report-mryiqgvh/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills