opp-repl-coverage-reports

Generate and analyze C++ coverage reports for opp_repl simulation runs.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tabgab/opp_repl-skill --skill opp-repl-coverage-reports
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opp-repl-coverage-reports
Source: https://github.com/tabgab/opp_repl-skill/tree/main/opp-repl-coverage-reports
Command: npx skills add https://github.com/tabgab/opp_repl-skill --skill opp-repl-coverage-reports

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coverage reports reveal which lines of C++ simulation source are executed by a run, helping you identify untested code paths and improve test coverage for opp_repl projects.

Core Features & Use Cases

  • Open the HTML coverage reports produced in coverage builds to inspect executed code paths.
  • Generate per-run or project-wide coverage data to guide test improvements and refactoring decisions.
  • Use case: determine which parts of a given simulation example exercise the code, then strengthen tests to cover gaps.

Quick Start

Run open_coverage_report on a chosen simulation project to build, run, and display the coverage HTML report.

Frequently Asked Questions about opp-repl-coverage-reports

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

FAQPage Schema
How do I generate C++ coverage reports for opp_repl simulation runs?

To generate C++ coverage reports for opp_repl simulation runs, use the open_coverage_report command on a chosen project. This builds the project in coverage mode, executes the simulation, and produces an HTML report for inspecting executed code paths.

Do I need LLVM tools to produce HTML coverage reports for C++ simulations?

Yes, producing HTML coverage reports requires LLVM tools, specifically llvm-profdata and llvm-cov. These tools process the raw profiling data generated during coverage builds and convert it into a viewable HTML format.

What is the best way to identify untested code paths in an opp_repl project?

The best way to identify untested code paths is to generate project-wide coverage data across representative configurations. Analyzing the resulting HTML coverage report reveals which C++ simulation source lines remain unexecuted, guiding test improvements.

Can I analyze coverage data for a single simulation run instead of a full project sweep?

Yes, you can analyze coverage data for a single simulation run. The tool supports both per-run and project-wide sweeps, allowing you to determine which parts of a specific simulation example exercise the code before scaling to broader configurations.

Why does my C++ simulation need to build in coverage mode?

Building in coverage mode instruments the C++ source code to track execution during the simulation run. This instrumentation is necessary to generate the raw profiling data that LLVM tools later parse into an HTML coverage report.

When should I use project-wide coverage sweeps over per-run coverage reports?

Use project-wide coverage sweeps across representative configurations when you need a comprehensive view of untested code paths across the entire project. Use per-run reports when focusing on how a specific simulation example exercises the code.