coverage-analysis

Analyze code coverage from fuzzing campaigns to assess harness effectiveness.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/iiammae/opero --skill coverage-analysis-iiammae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-analysis
Source: https://github.com/iiammae/opero/tree/main/.agents/skills/coverage-analysis
Command: npx skills add https://github.com/iiammae/opero --skill coverage-analysis-iiammae

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Coverage analysis helps you understand which parts of your code are being exercised during fuzzing, allowing you to assess harness effectiveness and identify potential blockers.

Core Features & Use Cases

  • Assess Harness Effectiveness: Evaluate which parts of your application are executed by fuzzing harnesses.
  • Identify Fuzzing Blockers: Discover magic value checks and other conditions that may hinder fuzzing progress.
  • Track Fuzzing Progress: Monitor how coverage changes with updates to harnesses, fuzzers, or the system under test (SUT).
  • Use Case: Use this Skill to establish a baseline for a new fuzzing campaign, verify harness improvements, or migrate between different fuzzers.

Quick Start

Run the coverage analysis Skill on your fuzzing campaign with the command: coverage-analysis run -c corpus -b baseline.

Frequently Asked Questions about coverage-analysis

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

FAQPage Schema
How do I measure code coverage in fuzzing campaigns to assess harness effectiveness?

To measure code coverage in fuzzing campaigns, you can automate analysis using this Skill to evaluate which application parts are executed by fuzzing harnesses. It supports multiple fuzzers and tools like LLVM and GCC to assess harness effectiveness.

What is the best way to identify fuzzing blockers during code coverage analysis?

Identifying fuzzing blockers during code coverage analysis involves discovering magic value checks and other conditions that hinder fuzzing progress. This Skill automates the detection of these blockers to help evaluate harness effectiveness.

Can I track fuzzing progress and establish a baseline for a new fuzzing campaign?

Yes, you can track fuzzing progress and establish a baseline for a new campaign by monitoring how coverage changes with updates to harnesses, fuzzers, or the system under test. Run the analysis using your corpus and baseline inputs.

Does code coverage analysis work with both LLVM and GCC coverage tools?

Yes, code coverage analysis works with both LLVM and GCC coverage tools. The Skill supports multiple fuzzers and code coverage tools, allowing you to assess harness effectiveness across different fuzzing environments.

Do I need specific knowledge of the fuzzer input format to run code coverage analysis?

Yes, you need knowledge of the fuzzer's input format and the system under test to run code coverage analysis. This prerequisite knowledge is required to properly automate the evaluation of harness effectiveness.

How do I verify harness improvements after migrating between different fuzzers?

To verify harness improvements after migrating between different fuzzers, use this Skill to compare code coverage results against your baseline. This allows you to track fuzzing progress and confirm the effectiveness of your new setup.