line-execution-checker
Check if specific lines were executed using gcov data
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: Line Execution Checker description: Check if specific lines were executed using gcov data version: 1.0 author: Claude tags:
- coverage
- gcov
- testing
Line Execution Checker
Purpose
Fast tool to check if specific source lines were executed during test runs.
Tool: line-checker
Build
g++ -O3 -std=c++17 line_checker.cpp -o line-checker
Usage
# Single line
./line-checker file.c:42
# Multiple lines
./line-checker file.c:42 main.c:100 util.c:55
Output
file.c:42 EXECUTED (5 times)
main.c:100 NOT EXECUTED
util.c:55 EXECUTED (12 times)
Exit Codes
- 0: All lines executed
- 1: One or more lines NOT executed
- 2: Error
Prerequisites
Coverage data must exist from prior test run with --coverage flag.
When User Asks
"Was line X of file.c executed?" or "Check if these lines were covered"
Steps
- Verify
.gcdafiles exist:find . -name "*.gcda" -print -quit - Build tool if needed:
g++ -O3 -std=c++17 line_checker.cpp -o line-checker - Run:
./line-checker file.c:X - Report result to user
Example Interaction
User: "Was line 127 in parser.c executed?"
./line-checker parser.c:127
# Output: parser.c:127 EXECUTED (3 times)
Response: "Yes, line 127 was executed 3 times during testing."
More by gadievron
View allrr-debugger: Deterministic debugging with rr record-replay. Use when debugging crashes, ASAN faults, or when reverse execution is needed. Provides reverse-next, reverse-step, reverse-continue commands and crash trace extraction.
github-archive: Investigate GitHub security incidents using tamper-proof GitHub Archive data via BigQuery. Use when verifying repository activity claims, recovering deleted PRs/branches/tags/repos, attributing actions to actors, or reconstructing attack timelines. Provides immutable forensic evidence of all public GitHub events since 2011.
Add gcov code coverage instrumentation to C/C++ projects
Generate, export, load, and verify forensic evidence from GitHub sources. Use when creating verifiable evidence objects from GitHub API, GH Archive, Wayback Machine, local git repositories, or security vendor reports. Handles evidence storage, querying, and re-verification against original sources.