line-execution-checker
starsforks
How to install line-execution-checker?
gadievron/raptor/line-execution-checker
$npx -y skills add gadievron/raptor --skill line-execution-checkerCheck if specific lines were executed using gcov data
SKILL.md
| 1 | # Line Execution Checker |
| 2 | |
| 3 | ## Purpose |
| 4 | Fast tool to check if specific source lines were executed during test runs. |
| 5 | |
| 6 | ## Tool: line-checker |
| 7 | |
| 8 | ### Build |
| 9 | ```bash |
| 10 | g++ -O3 -std=c++17 line_checker.cpp -o line-checker |
| 11 | ``` |
| 12 | |
| 13 | ### Usage |
| 14 | ```bash |
| 15 | # Single line |
| 16 | ./line-checker file.c:42 |
| 17 | |
| 18 | # Multiple lines |
| 19 | ./line-checker file.c:42 main.c:100 util.c:55 |
| 20 | ``` |
| 21 | |
| 22 | ### Output |
| 23 | ``` |
| 24 | file.c:42 EXECUTED (5 times) |
| 25 | main.c:100 NOT EXECUTED |
| 26 | util.c:55 EXECUTED (12 times) |
| 27 | ``` |
| 28 | |
| 29 | ### Exit Codes |
| 30 | - 0: All lines executed |
| 31 | - 1: One or more lines NOT executed |
| 32 | - 2: Error |
| 33 | |
| 34 | ## Prerequisites |
| 35 | Coverage data must exist from prior test run with `--coverage` flag. |
| 36 | |
| 37 | ## When User Asks |
| 38 | "Was line X of file.c executed?" or "Check if these lines were covered" |
| 39 | |
| 40 | ### Steps |
| 41 | 1. Verify `.gcda` files exist: `find . -name "*.gcda" -print -quit` |
| 42 | 2. Build tool if needed: `g++ -O3 -std=c++17 line_checker.cpp -o line-checker` |
| 43 | 3. Run: `./line-checker file.c:X` |
| 44 | 4. Report result to user |
| 45 | |
| 46 | ## Example Interaction |
| 47 | User: "Was line 127 in parser.c executed?" |
| 48 | |
| 49 | ```bash |
| 50 | ./line-checker parser.c:127 |
| 51 | # Output: parser.c:127 EXECUTED (3 times) |
| 52 | ``` |
| 53 | |
| 54 | Response: "Yes, line 127 was executed 3 times during testing." |
People who liked this also viewed
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026
- explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026
- minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026
- insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 2026
