lcov

Analyze LCOV coverage.info data to detect unexecuted lines, branches, and functions.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/multicam/ikigai-rev --skill lcov-multicam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lcov
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/lcov
Command: npx skills add https://github.com/multicam/ikigai-rev --skill lcov-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LCOV tooling helps developers identify gaps in test coverage by analyzing LCOV data and coverage.info to surface unexecuted lines, branches, and functions.

Core Features & Use Cases

  • Gaps detection: find uncovered lines, branches, and functions from coverage reports.
  • Format parsing: interpret coverage.info format (SF:, FN:, DA:, BRDA:, FNDA:) to derive actionable metrics.
  • Use Case: integrate into CI to fail builds when coverage drops or to generate targeted remediation tasks.

Quick Start

Run make check-coverage to generate coverage reports and inspect reports/coverage/coverage.info for gaps.

Frequently Asked Questions about lcov

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

FAQPage Schema
How do I find unexecuted lines and branches in a C++ coverage report?

To find unexecuted lines and branches in a C++ coverage report, you parse LCOV coverage data by inspecting coverage.info entries like DA: and BRDA: to surface specific code gaps.

What is the best way to automate coverage gap detection during CI?

Automating coverage gap detection during CI involves parsing LCOV coverage.info files to identify unexecuted lines, branches, and functions, enabling you to fail builds when coverage drops.

How does parsing LCOV coverage.info data help identify test gaps?

Parsing LCOV coverage.info data helps identify test gaps by interpreting format patterns such as SF:, FN:, DA:, BRDA:, and FNDA: to derive actionable metrics on unexecuted code.

Can I use LCOV gap analysis for local C/C++ testing workflows?

Yes, you can use LCOV gap analysis for local C/C++ testing workflows by running make check-coverage and inspecting the generated reports/coverage/coverage.info file to find uncovered code.

How do I identify uncovered functions in my LCOV test coverage data?

To identify uncovered functions in your LCOV test coverage data, you analyze the coverage.info file for FNDA: patterns, which track function execution counts and reveal unexecuted functions.