with one click
line-execution-checker
Check if specific lines were executed using gcov data
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Check if specific lines were executed using gcov data
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Instrument C/C++ with -finstrument-functions for execution tracing and Perfetto visualization
Add gcov code coverage instrumentation to C/C++ projects
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.
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.
Recover deleted commits from GitHub using REST API, web interface, and git fetch. Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches. Includes techniques for accessing "deleted" commits that remain on GitHub servers.
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.
| name | Line Execution Checker |
| description | Check if specific lines were executed using gcov data |
| version | 1 |
| author | Claude |
| tags | ["coverage","gcov","testing"] |
Fast tool to check if specific source lines were executed during test runs.
g++ -O3 -std=c++17 line_checker.cpp -o line-checker
# Single line
./line-checker file.c:42
# Multiple lines
./line-checker file.c:42 main.c:100 util.c:55
file.c:42 EXECUTED (5 times)
main.c:100 NOT EXECUTED
util.c:55 EXECUTED (12 times)
Coverage data must exist from prior test run with --coverage flag.
"Was line X of file.c executed?" or "Check if these lines were covered"
.gcda files exist: find . -name "*.gcda" -print -quitg++ -O3 -std=c++17 line_checker.cpp -o line-checker./line-checker file.c:XUser: "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."