skills.rest
ofelixdev
ofelixdevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

coverage-analysis

Analyzes code coverage from LLVM/GCC instrumentation to identify fuzzing blockers.

Updated Feb 24, 2026
Search Tags:#code analysis#security testing#coverage#llvm#fuzzing#gcc#harness effectiveness
One-click install
npx skills add https://github.com/ofelixdev/cc-kit --skill coverage-analysis-ofelixdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coverage-analysis
Source: https://github.com/ofelixdev/cc-kit/tree/main/template/skills/coverage-analysis
Command: npx skills add https://github.com/ofelixdev/cc-kit --skill coverage-analysis-ofelixdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you understand which parts of your code are being exercised by your fuzzing harnesses and identify potential blockers or areas for improvement in your fuzzing campaigns.

Core Features & Use Cases

  • Harness Effectiveness: Measure how well your fuzzing harnesses are covering your codebase.
  • Fuzzing Progress Tracking: Monitor changes in code coverage as you update fuzzers or the system under test.
  • Identify Fuzzing Blockers: Detect issues like magic value checks that prevent fuzzers from reaching certain code paths.
  • Use Case: After running a fuzzing campaign for a week, use this Skill to generate a coverage report and identify that only 30% of your critical parsing logic is being hit, indicating a need to improve your fuzzing strategy or add more seed inputs.

Quick Start

Use the coverage-analysis skill to generate an HTML report for the fuzzing corpus located in the 'corpus/' directory.

Frequently Asked Questions about coverage-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze code coverage from my fuzzing campaigns?▼

Code coverage analysis during fuzzing measures which code paths your harnesses exercise, helping identify under-tested logic and fuzzing blockers like magic value checks preventing deeper code execution.

How do I measure fuzzing harness effectiveness using gcovr?▼

You measure fuzzing harness effectiveness by generating coverage reports with gcovr or llvm-cov to quantify the percentage of your codebase hit during a fuzzing campaign, revealing gaps in execution paths.

Why does my fuzzer stop reaching certain code paths?▼

Fuzzers fail to reach code paths due to blockers like magic value checks. Coverage analysis detects these unexercised areas, indicating where to improve fuzzing strategy or add seed inputs.

Can I generate an HTML coverage report for a fuzzing corpus?▼

Yes, you can generate an HTML coverage report for a fuzzing corpus located in a directory to visualize code execution paths and track fuzzing progress over time as you update your harnesses.

Does coverage analysis work with both GCC and LLVM instrumentation?▼

Yes, coverage analysis works with both GCC and LLVM instrumentation, utilizing reporting tools like gcovr and llvm-cov respectively to generate comprehensive coverage reports for security auditing workflows.

Related Skills

Explore More Software Engineering Skills→
elizaOSelizaOS
19.0k

coverage-analysis

Analyze code coverage from fuzzing campaigns using llvm-cov and gcovr.

Official
Intermediate
mejangomejango

coverage-analysis

Identify unexercised code paths during fuzzing campaigns using LLVM coverage tools.

Community
Advanced
ayehiaaayehiaa

coverage-analysis

Analyzes code coverage from fuzzing campaigns to identify gaps and bottlenecks.

Community
Intermediate
RedHatProductSecurityRedHatProductSecurity
47

coverage-analysis

Measure instrumented code coverage during fuzzing and generate reports.

Official
Intermediate