cpp-static-analysis

Fix static analysis violations in C/C++ code from clang-tidy, cppcheck, Coverity, MISRA, AUTOSAR, and CERT reports.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Binh230199/ai --skill cpp-static-analysis-binh230199
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cpp-static-analysis
Source: https://github.com/Binh230199/ai/tree/main/.github/skills/cpp-static-analysis
Command: npx skills add https://github.com/Binh230199/ai --skill cpp-static-analysis-binh230199

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineers resolve static analysis findings in C and C++ code without introducing new violations or risky refactors.

Core Features & Use Cases

  • Fixes issues from clang-tidy, cppcheck, Coverity, MISRA C:2012, AUTOSAR C++14, and CERT C++ reports.
  • Groups findings by rule, prioritizes safety-critical problems first, and remediates one rule at a time.
  • Uses rule-specific reference guides, minimal code changes, post-fix checks, and justified suppressions only when a compliant fix is impossible.

Quick Start

Ask the skill to fix the provided static analysis report or rule ID in the affected C/C++ file and apply the safest rule-by-rule remediation.

Frequently Asked Questions about cpp-static-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix static analysis violations in C++ without introducing new issues?

You fix C++ static analysis violations safely by grouping findings by rule, remediating one rule at a time with minimal code changes, and running post-fix verification to prevent new issues.

Can I use this to clean up clang-tidy and cppcheck warnings across my codebase?

Yes, it remediates findings from clang-tidy, cppcheck, and Coverity by prioritizing safety-critical problems first and applying rule-specific reference guides for IDE warning cleanup.

How do I remediate MISRA C:2012 and AUTOSAR C++14 findings safely?

Remediate MISRA C:2012 and AUTOSAR C++14 findings by applying per-rule reference lookups and minimal code changes, using justified suppressions only when a compliant transformation is impossible.

What is the best way to handle C++ static analysis findings that cannot be fixed compliantly?

Handle unfixable C++ static analysis findings by applying justified suppressions only when a compliant transformation is impossible, ensuring the suppression is explicitly documented per rule.

Does this approach work for pre-commit review of C and C++ static analysis reports?

Yes, it supports pre-commit review and report-driven remediation by processing static analysis reports rule-by-rule and verifying that post-fix changes do not introduce new violations.