القائمة
Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | pi-release-workflow |
| description | Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks. |
| compatibility | Requires this Pi coding-agent monorepo release workflow. |
Use this when preparing, validating, or debugging package releases from this repo.
minimumReleaseAge; do not blindly bypass it for
fresh registry packages.pnpm-workspace.yaml or package
manifests intentionally, then run pnpm install to refresh the
lockfile.pnpm changeset status for pending release intent.pnpm install --frozen-lockfile to verify committed lockfile state.pnpm run preview:generate when preview image output should change.pnpm run check before release PRs or publishing.pi-package-sandbox-test for normal-user install/load
validation of published Pi packages.pnpm update -r --latest --catalog is not the safe catalog workflow
here.minimumReleaseAgeExclude;
that applies to registry packages.pnpx only when
appropriate.Use when running an existing /tmp Pi task harness. Executes inside the active contract, records status, respects enforcement, and loops through validation.
Use when creating executable /tmp Pi task harnesses for ambiguous or high-risk coding work. Builds contract, prompts, validation, logs, and enforcement rules.
Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.
Use when developing or reviewing packages/pi-observability dashboard/server changes locally, especially rebuilding dist, restarting the 43190 server, validating UI behavior, or keeping the local dashboard in sync with source edits.
Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.
Use when creating or modifying Pi extensions, built-in extension wiring, prompt shims, package scaffolds, package READMEs, or packages/pi-* implementation in this monorepo.