skills.rest
roberttmadsen13-del
roberttmadsen13-delCOMMUNITY
Explore all skills by this author →
GitHub

Line Execution Checker

Analyze gcov data to verify specific source lines executed during tests.

Updated Apr 28, 2026
Search Tags:#testing#c++#code-coverage#testing-tools#dynamic-analysis#gcov#line-execution
One-click install
npx skills add https://github.com/roberttmadsen13-del/TOURney --skill line-execution-checker-roberttmadsen13-del
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Line Execution Checker
Source: https://github.com/roberttmadsen13-del/TOURney/tree/main/SKILLS/raptor-main/.claude/skills/crash-analysis/line-execution-checker
Command: npx skills add https://github.com/roberttmadsen13-del/TOURney --skill line-execution-checker-roberttmadsen13-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool quickly verifies whether specific source lines were executed during test runs by analyzing gcov data, helping teams validate code coverage at the line level.

Core Features & Use Cases

  • Line-level execution checks to determine if designated lines were executed, enabling precise coverage validation.
  • GCov data integration to produce per-file line execution results across the codebase.
  • Use Case: After running tests, confirm that critical lines in core modules were executed to reduce risk and identify gaps in coverage.

Quick Start

To begin, run the tool on a target file and line, for example: line-checker file.c:42

Frequently Asked Questions about Line Execution Checker

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

FAQPage Schema
How do I check if a specific line of C++ code was executed during tests?▼

To verify if specific source lines were executed during tests, analyze gcov data files to produce per-file line execution results. This compares line references against execution counts to validate line-level coverage for critical paths in C/C++ projects.

What do I need to generate line execution results from gcov data?▼

Generating line execution results requires gcov data files (.gcda/.gcno) and a compiled test binary. These inputs enable the tool to compare line references against execution counts for C/C++ projects.

How do I validate line-level coverage for critical paths in C/C++ projects?▼

Validate line-level coverage for critical paths by analyzing gcov data to identify whether designated lines were executed. This confirms critical lines in core modules were reached during tests, reducing risk and identifying coverage gaps.

Can I verify code coverage at the line level using gcov data files?▼

Yes, you can verify code coverage at the line level using gcov data files (.gcda/.gcno). The tool analyzes this data to produce per-file line execution results, determining if specific source lines were executed during test runs.

What is the best way to identify gaps in line-level code coverage?▼

The best way to identify gaps in line-level code coverage is to analyze gcov data to check whether specific source lines were executed. This per-file line execution verification helps pinpoint critical lines that were not reached during tests.

Related Skills

Explore More Software Engineering Skills→
deonmenezesdeonmenezes
482

Code Coverage with gcov

Instrument C/C++ projects with gcov to generate coverage reports.

Community
Intermediate
yoshisadayoshisada

kiln-coverage

Enforce an 80% line and branch coverage gate for changed files.

Community
Intermediate
dawsonblockdawsonblock

Code Coverage with gcov

Instrument C/C++ programs with gcov to generate line, branch, and function coverage reports.

Community
Intermediate
gadievrongadievron
3.5k

Code Coverage with gcov

Instrument C/C++ projects with gcov to capture test coverage data.

Community
Basic