test-coverage-improver

To improve test coverage, run `make coverage` to generate reports, analyze the artifacts to pinpoint low-coverage files, and propose high-impact tests to systematically address gaps in your suite.

Analyzing coverage artifacts identifies untested code by parsing `.coverage` and `coverage.xml` reports to map executed lines, pinpointing specific files and lines with low or no test coverage.

The process for proposing new tests involves analyzing coverage reports to identify gaps, suggesting high-impact tests that prioritize critical code areas, and seeking explicit user approval before implementing them.

Yes, you can verify code quality improvements by rerunning coverage analysis and using code-change-verification to confirm that newly implemented tests successfully address identified coverage gaps.

Generating test coverage reports requires executing the `make coverage` command from the repository root to produce the necessary `.coverage` and `coverage.xml` artifacts for gap analysis.

A limitation of automated test gap identification is that it requires existing coverage artifacts to analyze, meaning you must execute coverage tools successfully first and approve proposed tests before implementation.