pack-and-copy

name

pack-and-copy

description

Validate a publisher package change against consumer repos by building + packing the publisher and installing the tarballs into each consumer, so consumer CI can run against the unmerged change. USE WHEN a publisher repo (e.g. a design system, shared library, SDK) has a pending change that needs to be tested in downstream repos before its version is merged and published. TRIGGER when user says "pack and copy", "pre-release test in consumers", "test this package change in <consumer>", "install the unreleased version into the apps", or "validate this change against <consumer repo>".

Pack and Copy

Validate a publisher package change against its consumer repos before the publisher's version bump is merged and published. The flow is:

1. Build the publisher package(s) — repo-specific, not automatable.
2. Run polygraph _pack-and-copy (or the pack_and_copy MCP tool) to pack them and install the tarballs into each consumer, rewriting package.json to a file: dependency.
3. Commit the consumer changes, including .polygraph-packages/*.tgz, to a branch, open a PR, and let consumer CI validate the change.

This skill covers steps 1 and 2. PR creation / CI monitoring is left to the polygraph and await-polygraph-ci skills.

Available Tools

Pack-and-copy functionality is available via both an MCP tool and a CLI command. Use whichever is available in your current environment.

MCP Tool	CLI Equivalent	Description
pack_and_copy	polygraph _pack-and-copy	Pack publisher packages and install tarballs into consumer repos for pre-release validation.