test-inventorylisted

Phase 1 of the test-readiness pipeline. Crawls a target repo, classifies every meaningful unit of code (business logic, service boundary, HTTP route, error path, external integration, user journey), prescribes the appropriate test layer (unit / integration / smoke / E2E) using the rubrics, ranks each by criticality (critical / high / medium), and tags canary eligibility. Outputs a deduplicated inventory — each functional unit appears exactly once at its canonical layer per the no-duplicate-coverage rule. Writes `docs/test-readiness/test-inventory.md`. Invoke when the `/test-inventory` command runs.
app-vitals/shipwright · ★ 6 · Testing & QA · score 71

Install: claude install-skill app-vitals/shipwright

# test-inventory skill ## Purpose Build the **inventory** — the source-of-truth ledger of what should be tested in this repo, at which layer, with what priority. ## When invoked By the `/test-inventory` command. The repo path arrives as `$ARGUMENTS` (defaults to `.`). ## Process ### Step 1 — detect the stack Read these signals to determine language and frameworks: - `package.json`, `tsconfig.json`, `bun.lock`, `pnpm-lock.yaml` → JS/TS - `pyproject.toml`, `requirements.txt`, `setup.py` → Python - `go.mod` → Go - `Gemfile` → Ruby - `Cargo.toml` → Rust - `pom.xml`, `build.gradle` → JVM Record stack profile (language, package manager, primary framework if obvious — e.g., Hono, Express, FastAPI, Rails). **CLAUDE.md layer-declaration convention:** also check the target repo's root `CLAUDE.md` for a section declaring its concrete layer structure (e.g. "handler → service → data", or whatever naming that repo uses — `architecture_layering` in `references/principles.md` is explicit that the layering principle concerns the *relationship* between layers, not literal names, and each repo's own `CLAUDE.md` should declare its concrete layer names). This mirrors the existing "## Testing" section pattern: `commands/review.md` extracts a repo's CLAUDE.md Testing section into `testReadinessContext` for `code-reviewer.md`'s test-readiness rule to consume, falling back to the universal baseline in `references/principles.md` when no such section exists. Apply the same fallback here — if t