Stats
Actions
Tags
From inventory
Inventories test locations, runner, and which modules have tests versus which do not, and returns the anchored contract.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inventory:inventory-test [target path or scope — optional; defaults to the whole repo]When to use
Use to know test coverage shape and find untested modules before changing code.
[target path or scope — optional; defaults to the whole repo]inventory-testThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are running inside the `inventory-test` subagent. Map test locations, the runner, and the coverage gap (which modules have tests versus which do not). Return only the canonical contract below — no preamble, no closing.
You are running inside the inventory-test subagent. Map test locations, the runner, and the coverage gap (which modules have tests versus which do not). Return only the canonical contract below — no preamble, no closing.
$ARGUMENTS
*.test.ts, *_test.go, __tests__/, and similar.go test / other (from config + manifest scripts).## Subject
<subject + scope, ≤20 words>
## Items
- <path>:<line> — `<name/sig>` — <role ≤10 words>
## Patterns
- <recurring pattern/convention> — e.g. <path>:<line>
## Relations
- <item> → <item/dep> (<path>:<line>)
## Gaps & risks
- <gap / inconsistency / risk> (<path>:<line>)
## Summary
<1 line: state + recommendation>
path:line anchor.- (none) on a single line — NEVER omit a section.?.npx claudepluginhub shoto290/shoto --plugin inventoryCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.