test-inventory

What problem does it solve?

This Skill turns a codebase into a clear testing inventory so teams can see what functional units exist, which layer should cover each one, and what to prioritize first.

Core Features & Use Cases

• Repository-wide classification: Scans the repo for meaningful units of code and groups them by business logic, service boundaries, routes, integrations, error paths, and user journeys.
• Canonical test-layer assignment: Assigns each unit to the lowest sufficient layer so coverage is not duplicated across unit, integration, smoke, and end-to-end tests.
• Priority and canary signals: Ranks items by criticality and flags which higher-layer checks are safe to run as canaries.
• Use case: A team preparing a new release can generate a single source-of-truth inventory before writing tests, making it easier to focus on the riskiest paths first.

Quick Start

Use the test-inventory skill to scan the repository, classify each meaningful code unit into its lowest sufficient test layer, rank criticality, and write docs/test-readiness/test-inventory.md.