coverage-full

Generate detailed code coverage reports with missed line numbers.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill coverage-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-full
Source: https://github.com/oscardlfr/AndroidCommonDoc/tree/main/skills/coverage-full
Command: npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill coverage-full

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The coverage-full skill addresses the need for a comprehensive overview of code coverage across all project modules, ensuring that no critical paths are overlooked.

Core Features & Use Cases

  • Comprehensive Coverage: Provides detailed coverage metrics for each module.
  • Customization: Allows inclusion of shared libraries and setting minimum missed lines.
  • Tool Selection: Supports multiple coverage tools like JaCoCo and Kover.
  • Use Case: Ideal for project documentation or preparing for a code review to demonstrate thorough testing.

Quick Start

Generate a full coverage report for your project by executing the command: '/coverage-full'

Frequently Asked Questions about coverage-full

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

FAQPage Schema
How do I generate a complete code coverage report for an Android project?

To generate a complete code coverage report for an Android project, use a tool that produces detailed metrics across multiple modules, including percentage covered and exact missed line numbers. This skill executes via the '/coverage-full' command.

Can I use JaCoCo and Kover for Kotlin Multiplatform coverage reports?

Yes, you can use JaCoCo and Kover for Kotlin Multiplatform coverage reports. This skill supports tool selection between these frameworks to calculate metrics, identify classes with missed lines, and output exact line numbers.

Does generating a full coverage report require specific environment variables?

Generating a full coverage report requires the ANDROID_COMMON_DOC environment variable to be set. The process operates strictly within the AndroidCommonDoc framework to analyze modules and produce detailed coverage metrics.

How do I include shared libraries in my project's coverage metrics?

To include shared libraries in your project's coverage metrics, customize the reporting configuration to add these dependencies. This ensures the comprehensive overview accounts for all critical paths across your modules.

What is the best way to identify classes with missed lines during a code review?

The best way to identify classes with missed lines during a code review is to generate a detailed coverage report. This skill outputs exact line numbers for missed code, ensuring no critical paths are overlooked before documentation or review.