Menu
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.
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.
Use when running repo scripts, adding or changing dependencies, editing package.json files, installing packages, or deciding how Bun workspace commands should be invoked in this monorepo.
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 bun run wt 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.
| 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 from the monorepo root:
bun run format
bun run lint
Useful check/fix pairs also run from the monorepo root:
bun run format:check
bun run format
bun run lint
bun run lint:fix
bun run lint:css
bun run lint:css:fix
For code changes, also run the relevant package-level typecheck:
cd <package-or-app>
bun run tsc
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:
cd packages/diffs && bun test
cd packages/trees && bun test
cd packages/truncate && bun test
Other packages and apps also expose local test scripts when relevant, for
example packages/path-store, packages/tree-test-data, and apps/docs.
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:
cd packages/trees && bun run coverage
cd packages/trees && bun run test:e2e
cd packages/path-store && bun run test:demo
cd apps/docs && bun run test:e2e
If E2E fixtures or dev servers are started in a worktree, follow the cleanup
contract from the worktrees-and-dev-servers skill.