Skill Detail

Publish installable pull-request package previews before release with pkg.pr.new

<p>Use pkg.pr.new when an agent needs an installable preview build from a pull request so reviewers can test a package before the maintainer cuts a real npm release.</p>

CI/CD IntegrationsMulti-Framework
CI/CD Integrations Multi-Framework Security Reviewed
⭐ 1.8k GitHub stars ⬇ 387.4k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill publish-installable-pull-request-package-previews-before-release-with-pkg-pr-new Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
A GitHub repository with Actions enabled, the pkg.pr.new GitHub App installed, Node.js/npm for the package build, and a package that can be built from CI.
Install & setup
<p>Install the <a href="https://github.com/apps/pkg-pr-new">pkg.pr.new GitHub App</a> on the repository, then add <code>npx pkg-pr-new publish</code> or a dev dependency on <code>pkg-pr-new</code> to your CI workflow. For monorepos, run the publish command once with all package paths so one workflow generates all preview URLs.</p>
Author
StackBlitz Labs
Publisher
Company
Last updated
Apr 13, 2026
Quick brief

pkg.pr.new gives an agent a narrow release-preview workflow. It builds package artifacts from commits or pull requests, exposes them through npm-compatible URLs, and lets reviewers install the preview immediately in downstream apps or reproduction repos. That is useful when the job is proving a library change in real conditions before merge or publish.

How it works

What this skill actually does

The boundary is clear enough to be skill-shaped. Invoke it when an agent needs temporary, installable PR previews for a package review or release workflow, not when the user wants a general package registry, CI platform, or npm publishing product. The job-to-be-done is preview-release distribution from pull requests without cutting a normal release.