// Validate Pi monorepo changes before reporting. Use after editing TypeScript, Svelte, package manifests, built-in registry, tests, or repo tooling.
| name | pi-validation-flow |
| description | Validate Pi monorepo changes before reporting. Use after editing TypeScript, Svelte, package manifests, built-in registry, tests, or repo tooling. |
| compatibility | Requires the Pi coding-agent monorepo validation scripts. |
Use this before saying implementation work is done.
git diff --name-only.pnpm --filter @spences10/<pkg> run check:self and
test:self.pnpm run check.pnpm run check:boundaries if available
or included by root check.pnpx check-skills validate <skill-path> --json after
every skill edit.Keep the final report short:
Compare proposed Pi customisation features with Pi built-in primitives before implementation. Applies to extensions, packages, slash commands, workflows, or speculative feature ideas.
Build or modify packages in this Pi monorepo. Use when creating Pi extensions, prompt shims, built-in extension wiring, package scaffolds, or packages/pi-* implementation work.
Use when verifying that published Pi packages from this repository install and load for normal Pi users without the repository wrapper. Applies to pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
Prepare or verify releases for this Pi monorepo. Use for Changesets, pnpm lockfile/versioning, package preview generation, release-age policy, or published package installability checks.