Line Execution Checker
Check if specific lines were executed using gcov data
Best use case
Line Execution Checker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Check if specific lines were executed using gcov data
Teams using Line Execution Checker should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/line-execution-checker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Line Execution Checker Compares
| Feature / Agent | Line Execution Checker | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Check if specific lines were executed using gcov data
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Line Execution Checker ## Purpose Fast tool to check if specific source lines were executed during test runs. ## Tool: line-checker ### Build ```bash g++ -O3 -std=c++17 line_checker.cpp -o line-checker ``` ### Usage ```bash # 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 1. Verify `.gcda` files exist: `find . -name "*.gcda" -print -quit` 2. Build tool if needed: `g++ -O3 -std=c++17 line_checker.cpp -o line-checker` 3. Run: `./line-checker file.c:X` 4. Report result to user ## Example Interaction User: "Was line 127 in parser.c executed?" ```bash ./line-checker parser.c:127 # Output: parser.c:127 EXECUTED (3 times) ``` Response: "Yes, line 127 was executed 3 times during testing."
Related Skills
yt-outline
Build detailed step-by-step YouTube video outlines with demo prep, screen-share sequences, and visual planning. Use this skill whenever the user says "create an outline", "outline this video", "video outline", "build the outline", "production outline", or has an approved brief and packaging and needs the final pre-production document before demo prep and filming. Use when working with yt outline. Trigger with 'yt', 'outline'.
vertex-ai-pipeline-creator
Vertex Ai Pipeline Creator - Auto-activating skill for GCP Skills. Triggers on: vertex ai pipeline creator, vertex ai pipeline creator Part of the GCP Skills skill category.
tutorial-outline-creator
Tutorial Outline Creator - Auto-activating skill for Technical Documentation. Triggers on: tutorial outline creator, tutorial outline creator Part of the Technical Documentation skill category.
soc2-compliance-checker
Soc2 Compliance Checker - Auto-activating skill for Security Advanced. Triggers on: soc2 compliance checker, soc2 compliance checker Part of the Security Advanced skill category.
sklearn-pipeline-builder
Sklearn Pipeline Builder - Auto-activating skill for ML Training. Triggers on: sklearn pipeline builder, sklearn pipeline builder Part of the ML Training skill category.
presentation-slide-outliner
Presentation Slide Outliner - Auto-activating skill for Visual Content. Triggers on: presentation slide outliner, presentation slide outliner Part of the Visual Content skill category.
preprocessing-data-with-automated-pipelines
Process automate data cleaning, transformation, and validation for ML tasks. Use when requesting "preprocess data", "clean data", "ETL pipeline", or "data transformation". Trigger with relevant phrases based on skill purpose.
pipeline-monitoring-setup
Pipeline Monitoring Setup - Auto-activating skill for Data Pipelines. Triggers on: pipeline monitoring setup, pipeline monitoring setup Part of the Data Pipelines skill category.
performance-baseline-creator
Performance Baseline Creator - Auto-activating skill for Performance Testing. Triggers on: performance baseline creator, performance baseline creator Part of the Performance Testing skill category.
orchestrating-deployment-pipelines
Deploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
linear-issue-generator
Linear Issue Generator - Auto-activating skill for Enterprise Workflows. Triggers on: linear issue generator, linear issue generator Part of the Enterprise Workflows skill category.
jenkins-pipeline-intro
Jenkins Pipeline Intro - Auto-activating skill for DevOps Basics. Triggers on: jenkins pipeline intro, jenkins pipeline intro Part of the DevOps Basics skill category.