line-execution-checker
Checks if specific source code lines were executed using gcov coverage files.
Install
mkdir -p .claude/skills/line-execution-checker && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6871" && unzip -o skill.zip -d .claude/skills/line-execution-checker && rm skill.zipInstalls to .claude/skills/line-execution-checker
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Check if specific lines were executed using gcov dataKey capabilities
- →Verify execution counts for specific lines
- →Identify uncovered code branches
- →Report execution status for multiple files
How it works
The tool compiles a checker that reads .gcda coverage files to verify if specific source lines were executed during testing.
Inputs & outputs
When to use line-execution-checker
- →Checking test coverage for specific lines
- →Debugging uncovered branches
- →Verifying test execution results
About this skill
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."
When not to use it
- →Projects without gcov coverage data
- →Non-C/C++ source code
Prerequisites
Limitations
- →Requires existing .gcda files
- →Only supports C/C++
How it compares
It provides a direct command-line interface to query specific line coverage instead of manually parsing large coverage reports.
Compared to similar skills
line-execution-checker side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| line-execution-checker (this skill) | 1 | 4mo | Review | Beginner |
| webapp-testing | 353 | 3mo | Review | Intermediate |
| ui-ux-expert-skill | 91 | 9mo | Review | Advanced |
| skill-creator | 128 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by gadievron
View all by gadievron →You might also like
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-ux-expert-skill
fercracix33
Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.
skill-creator
anthropics
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
playwright-mcp
sfc-gh-dflippo
Browser testing, web scraping, and UI validation using Playwright MCP. Use this skill when you need to test Streamlit apps, validate web interfaces, test responsive design, check accessibility, or automate browser interactions through MCP tools.