analyzing-unit-tests

To analyze unit-test coverage across multi-module codebases, apply this Skill to the service, domain, and utilities layers. It identifies coverage gaps and documents test patterns, producing a structured report under docs/unwind/layers/unit-tests/.

Documenting unit-test patterns and common utilities involves scanning isolated components to map existing test code. This Skill generates structured, machine-readable per-domain test documents that link directly to source files without adding commentary.

Yes, you can generate a machine-readable report of test coverage for service and domain layers. The Skill produces an index.md and specific test documents under docs/unwind/layers/unit-tests/ to ensure completeness and direct source linkage.

Yes, this unit-test analysis tool works without external dependencies or components. It operates independently to analyze isolated test components and incrementally writes the aggregated coverage data directly into your documentation directory.

To start outlining test documentation for isolated code components, create the initial index and begin generating service-tests.md, domain-tests.md, utilities.md, and coverage-gaps.md files to structure your aggregated test analysis.