What problem does it solve? It answers the question of whether your feature code is adequately tested by systematically mapping source files to their unit, integration, and E2E tests, then surfacing exactly which methods, branches, and error paths lack coverage. ## Core Features & Use Cases - Three-Layer Coverage Mapping: Cross-references feature documentation with source code to build an inventory of Unit / Integration / E2E test coverage per module. - Gap Classification: Categorizes missing tests by severity (Critical, Major, Minor, Nice-to-have) based on whether they involve core logic, data writes, error handling, or edge cases. - Actionable Report: Produces a structured Markdown report with coverage tables, gap lists, and a prioritized plan of recommended new tests. - Use Case: After shipping a payment feature, run this Skill against the feature docs to discover that refund error handling has no integration tests and amount rounding branches are untested, then get a prioritized test-writing plan. ## Quick Start Ask the agent to check test coverage for the feature documentation at a given path, for example: check coverage for docs/features/payment-refund.md.
