layer-testing

Layer testing automates test creation across core, domain, application, infrastructure, and boundary layers in Hexagonal, Clean, and Layered architectures. It uses coverage-first analysis to identify gaps, then guides you through generating focused tests for your specified layer without modifying production code.

Coverage-first analysis runs an initial coverage pass on your target layer to determine existing test gaps before writing anything. This approach prioritizes which tests to create based on actual coverage data rather than guessing.

Layer testing uses isolated git worktrees to run all changes in a separate environment. This keeps your working branch clean while you develop and validate tests for a specific layer, then merge only verified changes back.

You can provide an optional playbook to drive your testing strategy, or the Skill guides you through an interactive template to select a layer-focused approach. Either path leads to consistent, coverage-driven test generation.

Layer testing performs stepwise verification through coverage checks and quality gates to validate that your new tests meet coverage targets and maintain code quality before you integrate changes back into your main branch.

Yes—provide your Module and Layer names to start. The Skill uses these parameters along with an optional Playbook path to create the isolated worktree and begin coverage analysis for your specified architectural layer.