142 skills · sorted by relevance
Investigate memory growth and out-of-memory failures in OpenClaw tests. Compare memory measurements and heap snapshots, records of objects held in memory, to distinguish cleanup leaks from retained test modules and verify targeted fixes.
Evaluate Vitest tests by the observable behavior and realistic regressions they protect. Guide new test authoring and review existing suites for duplication, dependence on implementation details, and code used only by tests, with evidence for retention or removal.
Choose and run checks for TypeScript SDK changes, including type checks, linting, builds, Vitest suites, and tests of complete runtime flows. Also guides writing or adapting CLI tests for Effect v4.
Write JavaScript and TypeScript tests with Jest, Vitest, and Testing Library. Covers functions, UI components, and APIs, including mock replacements for external services, reusable test data, and setup for automated testing.
Explore an existing Vitest 3.2 JSON test report to count results, search failed tests, and inspect file errors. Review original diagnostic details and keep tentative explanations separate from evidence, without launching tests.
Build and review Cloudflare Durable Objects for applications that retain shared state, such as chat rooms, games, and booking systems. Covers SQLite storage, remote method calls, WebSockets, scheduled work, Workers integration, configuration, and Vitest tests.
Set up and refine web projects with Vite, a tool for running development servers and building production files. It covers framework integration, environment settings, live code updates, testing configuration, and splitting code to improve loading.
Vitest 5 (Vite ネイティブテストフレームワーク) リファレンス。 test, describe, it, expect, vi.fn, vi.mock, vi.spyOn, vi.when、 beforeEach / afterEach、test.extend fixtures、test tags / annotations、 coverage (v8 / istanbul)、snapshot、vitest.config.ts、projects (old workspace)、 Vitest Browser Mode (vitest-browser-react, locators, expect.element)、UI モード、bench fixture。
The English summary is being prepared. Showing the original description.
Write or repair React tests around user actions and visible results. Cover components and hooks, simulate network responses, check accessibility, and decide when real browser component tests or end-to-end tests across pages are needed.
Create Vitest tests for Mastra playground features using MSW to simulate network responses. Exercise the real client SDK, React Query cache, and components with typed sample data to check loading, access conditions, redirects, and errors.
Create tests for Convex functions with convex-test and vitest, using a backend that runs in memory. Check arguments, return values, authentication, indexes, errors, and scheduled functions without relying on real time or network access.
Set up Vitest testing in any project — detects type (Cloudflare Workers, React, Node, library), generates vitest.config.ts, test setup, utilities, and a sample test. Covers mocking patterns, coverage config, workspace setup, Jest migration. Use whenever the user mentions adding tests, setting up Vitest, configuring tests, migrating from Jest, fixing testing infrastructure, or asks 'how do I test this'.
The English summary is being prepared. Showing the original description.
Vitest testing framework patterns and best practices. Use when writing unit tests, integration tests, configuring vitest.config, mocking with vi.mock/vi.fn, using snapshots, or setting up test coverage. Triggers on describe, it, expect, vi.mock, vi.fn, beforeEach, afterEach, vitest.
The English summary is being prepared. Showing the original description.
Assists with unit and integration testing using Vitest, a Vite-native test runner. Use when writing tests, configuring mocks, setting up coverage, or migrating from Jest. Trigger words: vitest, unit testing, test runner, vi.fn, vi.mock, test coverage, jest replacement.
The English summary is being prepared. Showing the original description.
Maintain visual snapshot tests, which compare rendered images, for Remotion’s web renderer. Update existing tests after implementation changes, or add explicitly requested tests with sample components, preview registration, and documentation updates for supported properties.
Write integration tests for core error processors by simulating API failures with a mock model. Check retry attempts, changes to conversation messages, and streamed responses, with guidance on test setup and diagnosing empty output.
Build Vue 3 applications using JavaScript and JSDoc comments that describe data types. Create components and reusable logic, configure Vite, routing, and state management, and check annotations and behavior with ESLint and Vitest.
Tests a specific Convex feature with sample data and simulated users, without deployment. It checks expected results, rejects unauthorized callers, and verifies that queries return only data belonging to the current user.
Write, review, filter, mock, and debug Core unit tests with the repository's installed Vitest 5 configuration. Use for tests under Core's Vitest include paths, `vi.mock`/spies/timers, jsdom component tests, coverage output, focused reruns, or unit-test failures. Do not use for browser E2E flows or async Next.js Server Components.
The English summary is being prepared. Showing the original description.
Migrate a test suite from one framework to another, incrementally and without losing coverage. Covers Selenium→Playwright, Cypress→Playwright, Jest→Vitest, Mocha→Vitest, and Protractor→Playwright, with parallel CI running, locator/assertion translation, and a coverage-parity track. Use when: "migrate tests," "switch framework," "Selenium to Playwright," "Jest to Vitest," "framework migration." Not for: bulk selector regeneration after a UI refactor on the SAME framework — use selector-drift-recovery. Not for: healing one flaky test at runtime — use test-reliability. Not for: modernizing patterns without changing framework — use ai-qa-review. Related: playwright-automation, cypress-automation, unit-testing, ci-cd-integration, test-reliability.
The English summary is being prepared. Showing the original description.
Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.
The English summary is being prepared. Showing the original description.
Use this skill when writing unit tests, mocking dependencies, testing pure functions, or measuring coverage with Vitest. Trigger words: ユニットテスト, 単体テスト, Vitest, モック, テストを書く, カバレッジ, describe, it, expect, vi.mock.
The English summary is being prepared. Showing the original description.
Review new and existing software tests for the behavior and regressions they actually protect. Identify duplicate or implementation-dependent checks, document evidence before removal, and simplify code used only by tests while retaining meaningful coverage.
Review and test OpenClaw Control UI changes with galleries of screen states and real browser flows. Use simulated Gateway responses to check behavior consistently, collect feedback, and capture screenshots or videos as evidence.