Skip to content
Back to skills

Line Execution Checker

ASecurity

Check if specific lines were executed using gcov data

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 12, 2026
ai-agentsgoc++bashtestinggit

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add thedixitjain/the-mega-skill-library --skill line-execution-checker --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Line Execution Checker?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Line Execution Checker
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedixitjain-line-execution-checker/badge)](https://www.skillsdirectory.com/skills/thedixitjain-line-execution-checker)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: line-execution-checker
description: "Check if specific lines were executed using gcov data"
category: general-purpose
source_repo: gadievron/raptor
source_path: ".claude/skills/crash-analysis/line-execution-checker/SKILL.md"
source_url: https://github.com/gadievron/raptor/blob/HEAD/.claude/skills/crash-analysis/line-execution-checker/SKILL.md
---


# 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."

---

**Source:** [`gadievron/raptor`](https://github.com/gadievron/raptor) → `.claude/skills/crash-analysis/line-execution-checker/SKILL.md`

Files in this skill

  • SKILL.md1.6 KB
  • line_checker.cpp4.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.