菜单
Use when adding or running tests, checking snapshots, choosing between Bun tests and Playwright, running lint/format/typecheck, or deciding the verification scope for a change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when running repo scripts, adding or changing dependencies, editing package.json files, installing packages, publishing packages, or deciding when pnpm package operations versus Bun runtime commands should be invoked.
Use when adding or changing packages/apps, TypeScript configs, workspace dependencies, package references, exports, or monorepo project-reference relationships.
Use when working with the repo's moonx root:wt worktree helper, Pierre-managed worktrees, dev-server port offsets, stale server cleanup, Playwright fixtures, or Chrome debug instances. Do not use this as a substitute for host-provided workspace isolation.
Use when preparing, splitting, reviewing, or creating git commits in this repo, especially after larger implementations that should be broken into independently verified commits.
Use when opening, inspecting, clicking, filling, snapshotting, or otherwise automating web pages for this repo, including local dev servers and browser-based verification.
Use when changing loops, collection processing, invalidation logic, tree/diff traversal, path scanning, virtualized rendering calculations, or any code where repeated scans or boolean control flow affect performance or correctness.
| name | testing-and-verification |
| description | Use when adding or running tests, checking snapshots, choosing between Bun tests and Playwright, running lint/format/typecheck, or deciding the verification scope for a change. |
After code changes, run the required baseline (moon tasks run from anywhere in the repo, including CI-marked agent shells):
moon run root:format root:lint
Useful check/fix pairs on the root project:
moon run root:format-check
moon run root:format
moon run root:lint
moon run root:lint-fix
moon run root:lint-css
moon run root:lint-css-fix
For code changes, also run the relevant typecheck (moon builds workspace dependencies first automatically):
moonx <project>:typecheck
# or, scoped to what actually changed:
moonx :typecheck --affected
Use Bun's built-in test runner. Tests usually live in a test/ folder inside
each package and use describe, test, and expect from bun:test.
Prefer unit or integration tests by default:
moonx diffs:test
moonx trees:test
moon run :test runs every project's suite. Tests import workspace dependencies
through their built dist, so moon builds those first; running bun test
directly inside a package also works when dist is fresh.
Bun supports toMatchSnapshot(). Avoid new snapshot coverage unless it is
shallow and narrowly scoped to the exact behavior under test.
Update snapshots from the package directory:
bun test -u
Add Playwright/browser E2E tests only when behavior cannot be validated without a real browser engine. Good candidates include computed style checks, shadow DOM boundaries, and browser-only rendering behavior.
Keep E2E coverage small and high-value:
moonx trees:coverage
moonx trees:test-e2e
moonx path-store:test-demo
moonx docs:test-e2e
If E2E fixtures or dev servers are started in a worktree, follow the cleanup
contract from the worktrees-and-dev-servers skill.