coverage-report

A unified code coverage report for a polyglot codebase aggregates outputs from various language-specific tools. This skill detects formats like Cobertura, JaCoCo, and lcov, parsing them into a single structured report with pass/fail thresholds.

Supported coverage formats include Cobertura, JaCoCo, lcov, json-summary, and go-cover. The system detects the format produced by your language-specific tooling and parses the outputs into a unified, readable report.

Yes, you can enforce a configurable threshold on code coverage results. The skill applies the threshold to parsed coverage data, generating an overall pass or fail status for the repository to help QA assess test coverage.

Yes, language-agnostic code coverage reporting works without language-specific tooling. It uses shell tools or Python to resolve the target repository, detect the coverage format, and produce a structured, readable report across diverse codebases.

Aggregating JaCoCo and Cobertura coverage data is best handled by a language-agnostic reporting tool that dispatches by coverage format. This approach parses outputs from both tools, generating a unified per-package coverage view.

A limitation is that the analysis is read-only and relies on existing coverage data produced by separate tooling. It assesses test coverage across diverse codebases but does not execute tests itself, requiring pre-generated outputs.