Run any Skill in Manus with one click

$pwd:

pi-validation-flow

Name: Pi Validation Flow
Author: spences10

// Validate Pi monorepo changes before reporting. Use after editing TypeScript, Svelte, package manifests, built-in registry, tests, or repo tooling.

Run Skill in Manus

$ git log --oneline --stat

stars:37

forks:7

updated:May 23, 2026 at 16:44

SKILL.md

readonly

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.

Pi Validation Flow

Use this before saying implementation work is done.

Workflow

Inspect changed files with git diff --name-only.
Run the narrowest package validation for changed packages.
Run LSP diagnostics for changed TypeScript/Svelte source files.
Run root validation when shared files, root scripts, package manifests, lockfile, or built-in registry changed.
Report failures honestly: separate new failures, pre-existing failures, skipped checks, and unavailable tools.

Command selection

Single package: pnpm --filter @spences10/<pkg> run check:self and test:self.
Root/shared changes: pnpm run check.
Boundary-sensitive changes: pnpm run check:boundaries if available or included by root check.
Svelte files: use Svelte-specific validation and LSP diagnostics.
Skills: run pnpx check-skills validate <skill-path> --json after every skill edit.

Reporting format

Keep the final report short:

Changed: files/packages touched.
Validation: commands run and results.
Risks: only unresolved failures or skipped checks.

related-skills.json

same repository

pi-primitive-check.md

from "spences10/my-pi"

Compare proposed Pi customisation features with Pi built-in primitives before implementation. Applies to extensions, packages, slash commands, workflows, or speculative feature ideas.

2026-05-2537

pi-extension-development.md

from "spences10/my-pi"

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.

2026-05-2337

pi-package-sandbox-test.md

from "spences10/my-pi"

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.

2026-05-2337

pi-release-workflow.md

from "spences10/my-pi"

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.

2026-05-2337

package.json

"author": "spences10"

"repository": "spences10/my-pi"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

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.

Pi Validation Flow

Use this before saying implementation work is done.

Workflow

Inspect changed files with git diff --name-only.
Run the narrowest package validation for changed packages.
Run LSP diagnostics for changed TypeScript/Svelte source files.
Run root validation when shared files, root scripts, package manifests, lockfile, or built-in registry changed.
Report failures honestly: separate new failures, pre-existing failures, skipped checks, and unavailable tools.

Command selection

Single package: pnpm --filter @spences10/<pkg> run check:self and test:self.
Root/shared changes: pnpm run check.
Boundary-sensitive changes: pnpm run check:boundaries if available or included by root check.
Svelte files: use Svelte-specific validation and LSP diagnostics.
Skills: run pnpx check-skills validate <skill-path> --json after every skill edit.

Reporting format

Keep the final report short:

Changed: files/packages touched.
Validation: commands run and results.
Risks: only unresolved failures or skipped checks.

pi-validation-flow

Pi Validation Flow

Workflow

Command selection

Reporting format

More from this repository

More from this repository

Pi Validation Flow

Workflow

Command selection

Reporting format