pi-release-workflow

Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability…

Skill by victorhg

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/victorhg-pi-release-workflow

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.

Use cases: productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/pi-release-workflow

What's inside

Skill 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.
License: MIT
Compatibility: Requires this Pi coding-agent monorepo release workflow.
Instructions: 38 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Pi Release Workflow

Use this when preparing, validating, or debugging package releases
from this repo.

## Workflow

1. Check current package changes and Changesets before editing
   versions.
2. Respect pnpm `minimumReleaseAge`; do not blindly bypass it for
   fresh registry packages.
3. For catalog/version updates, edit `pnpm-workspace.yaml` or package
   manifests intentionally, then run `pnpm install` to refresh the
   lockfile.
4. Regenerate release artifacts when required, especially
   startup/package preview assets.
5. Validate locally, then test published-package installability with
   the sandbox skill when applicable.

## Commands and checks

- `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.
- Use `pi-package-sandbox-test` for normal-user install/load
  validation of published Pi packages.

## Pitfalls from recent sessions

- `pnpm update -r --latest --catalog` is not the safe catalog workflow
  here.
- Local workspace packages do not need `minimumReleaseAgeExclude`;
  that applies to registry packages.
- If a validator is missing, report it and use `pnpx` only when
  appropriate.

From victorhg/pi-dev, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Jul 9, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/victorhg/pi-dev
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from victorhg

Cite this page

pi-release-workflow skill. Agent Mart. https://agentmart.dev/skills/victorhg-pi-release-workflow (last updated 2026-10-24)