Review test strategy
Review test strategy and regression resistanceFrom its SKILL.md
npx -y skills add yida29/archrip --skill review-test-strategyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.9 KB, as published. Nobody here has run it
Test strategy review — regression resistance & minimal effective tests
Review the repo’s current test coverage and propose the smallest set of tests that prevents common regressions.
What to look for
- Existing test runners / scripts / CI workflows (or absence)
- Most fragile boundaries: CLI flows (init/build/serve), schema validation, layout, viewer loading
- Contract tests: schema vs examples/templates/docs
- Packaging tests: published artifacts include required templates/schema assets
Output format
- Current state (what exists, what doesn’t)
- High-value tests (ordered)
- unit/contract/E2E smoke (keep it minimal)
- CI suggestion (if none): run typecheck/build + a small smoke test
$ARGUMENTS