test-coverage-improver

To identify test coverage gaps in a JavaScript monorepo, run coverage analyses across packages and parse artifacts like coverage-summary.json and lcov.info to highlight under-covered files and branches.

Generating concrete test ideas from coverage analysis involves parsing coverage summaries to find the lowest-coverage files and under-80% branches, then drafting specific test proposals for each gap.

Yes, this test coverage analysis works with monorepos containing multiple packages by coordinating coverage runs across the workspace and aggregating results into unified summary artifacts.

The process for adding tests after finding coverage gaps requires prompting for user approval before implementation, adding the proposed tests, and rerunning the coverage suite to verify improvements.

To analyze missing tests, the required coverage artifacts are coverage-summary.json and lcov.info, which are collected by executing the coverage workflow at the repository root.

No, you cannot automatically add tests without approval in this coverage workflow; it explicitly prompts for user confirmation before adding any tests to ensure proposed changes are reviewed.