test-inventory

Scan repositories and classify code units into deduplicated test layers.

9|2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill test-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-inventory
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/test-inventory
Command: npx skills add https://github.com/app-vitals/shipwright --skill test-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about test-inventory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a test inventory for a repository with multiple layers?

Build a test inventory by scanning your repository, classifying code units by business logic, service boundaries, and routes, then assigning each to its lowest sufficient test layer to avoid coverage duplication.

What is canonical test-layer assignment for code coverage planning?

Canonical test-layer assignment maps each functional code unit to the lowest sufficient layer—unit, integration, smoke, or E2E—ensuring coverage is not duplicated across multiple testing levels.

How do I determine canary eligibility for end-to-end tests?

Determine canary eligibility by ranking code units by criticality and flagging which higher-layer checks are safe to run as canaries during release preparation.

Does the test inventory classification work with existing CLAUDE.md layer conventions?

Yes, the classification uses stack detection and applies CLAUDE.md layer conventions when present to deduplicate units and assign appropriate test coverage across your codebase.

What's the best way to plan test coverage for external integrations and error paths?

Plan coverage by scanning the repo for external integrations and error paths, grouping them into meaningful units, and assigning each to the lowest sufficient test layer with criticality rankings.

Where should I document the generated test readiness inventory?

Document the generated test readiness inventory by writing the classified code units, assigned test layers, and criticality rankings to docs/test-readiness/test-inventory.md.