How do I install the Testing And Verification skill?

Run npx skillmds@latest add pierrecomputer/testing-and-verification in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Testing And Verification safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Testing And Verification?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Testing And Verification free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Testing And Verification?

pierrecomputer (@pierrecomputer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Testing And Verification by pierrecomputer

Name: Testing And Verification
Author: pierrecomputer

File contents

Testing and Verification

Baseline Commands

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

Unit and Integration Tests

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.

Snapshots

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

Browser and E2E Tests

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.

---name: testing-and-verificationdescription: 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.---# Testing and Verification## Baseline CommandsAfter code changes, run the required baseline (moon tasks run from anywhere inthe repo, including CI-marked agent shells):```bashmoon run root:format root:lint```Useful check/fix pairs on the root project:```bashmoon run root:format-checkmoon run root:formatmoon run root:lintmoon run root:lint-fixmoon run root:lint-cssmoon run root:lint-css-fix```For code changes, also run the relevant typecheck (moon builds workspacedependencies first automatically):```bashmoonx <project>:typecheck# or, scoped to what actually changed:moonx :typecheck --affected```## Unit and Integration TestsUse Bun's built-in test runner. Tests usually live in a `test/` folder insideeach package and use `describe`, `test`, and `expect` from `bun:test`.Prefer unit or integration tests by default:```bashmoonx diffs:testmoonx trees:test````moon run :test` runs every project's suite. Tests import workspace dependenciesthrough their built dist, so moon builds those first; running `bun test`directly inside a package also works when dist is fresh.## SnapshotsBun supports `toMatchSnapshot()`. Avoid new snapshot coverage unless it isshallow and narrowly scoped to the exact behavior under test.Update snapshots from the package directory:```bashbun test -u```## Browser and E2E TestsAdd Playwright/browser E2E tests only when behavior cannot be validated withouta real browser engine. Good candidates include computed style checks, shadow DOMboundaries, and browser-only rendering behavior.Keep E2E coverage small and high-value:```bashmoonx trees:coveragemoonx trees:test-e2emoonx path-store:test-demomoonx docs:test-e2e```If E2E fixtures or dev servers are started in a worktree, follow the cleanupcontract from the `worktrees-and-dev-servers` skill.

Frequently asked questions

Testing And Verification