coverage-analyzer
SolidParse coverage.py XML reports (coverage.xml) into a human-readable coverage analysis: total line/branch percent, files with zero coverage, worst-10 ranking, delta vs a stored JSON baseline, and a PASS/FAIL verdict against an optional threshold. Stdlib-only Python script (xml.etree.ElementTree, json, argparse) that closes the loop after test-generator.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- bestdeejay-design
- Repository
- bestdeejay-design/agent-skills
- Created
- 1 months ago
- Last Updated
- 2 weeks ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
code-coverage
When the user wants to measure, interpret, or improve code coverage — line, branch, function, statement, condition, MC/DC coverage. Use when the user mentions "code coverage," "test coverage," "Istanbul," "c8," "JaCoCo," "coverage.py," "Coverlet," "lcov," "Codecov," "Coveralls," "branch coverage," "MC/DC," or "coverage threshold." For test-quality signal beyond coverage see mutation-testing. For strategy framing see test-strategy.
coverage
Code coverage skills: fix low coverage, enforce thresholds in CI, or audit coverage.config.xml for drift. Determines mode from user intent automatically. Triggers on: coverage fix, low coverage, improve coverage, fix low coverage, coverage gate, coverage threshold, enforce coverage, minimum coverage, coverage enforcement, add coverage gate, audit coverage config, coverage config drift, coverage.config.xml, check coverage targets, fix coverage config, stale coverage config, coverage missing project, coverage work, coverage skill.
test-coverage-analyzer
Find the gaps between what was required and what was actually tested. Use when a lead says "where are our coverage gaps", "what isn't tested", or wants requirements checked against the designed, automated, and executed tests. Builds a traceability view across Requirement → Acceptance Criteria → Test Case → Automation → Execution, then surfaces untested requirements, thin coverage, executed-but-failing coverage, and orphan tests — ranked by risk. Reports only from supplied artifacts; never assumes coverage without traceable evidence.