w-test
Run the repository test scripts and fix failures until they pass.
Install
npx skills add https://github.com/blockmatic/basilic-skills --skill w-testSKILL.md
Run the documented test scripts from package.json (filtered to the change when the repo supports it). Fix owning causes. Do not publish.
- Identify the test command for the affected packages (
pnpm test, Turbo filters, or the app E2E script). Prefer the narrowest suite that covers the change; use the full suite when the failure is unknown or the user asked for it. - Run the command. Capture failing tests, not a paraphrase.
- Fix one owning cause at a time. Re-run the failed command. Do not weaken assertions or skip tests to obtain a pass. Stop when the suite is green or remaining failures need a human (secrets, env, flaky infra).
- Docs:
/w-docsif behavior or commands changed.
Related skills
tddmattpocock979KTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.diagnosing-bugsmattpocock678KDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.migrate-to-shoehornmattpocock388KMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.systematic-debuggingobra275KUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes