001-release-package

Packs and verifies the mydevkit extension package through a consumer workspace installation test.

1|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/flaviostutz/xdrs-core --skill 001-release-package-flaviostutz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 001-release-package
Source: https://github.com/flaviostutz/xdrs-core/tree/main/examples/mydevkit/.xdrs/mydevkit/adrs/principles/skills/001-release-package
Command: npx skills add https://github.com/flaviostutz/xdrs-core --skill 001-release-package-flaviostutz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing an XDRS extension package without verifying that consumers can actually install and run it leads to broken downstream workspaces. This Skill provides a repeatable procedure to pack the mydevkit package, validate it in a consumer fixture, and publish with confidence. ## Core Features & Use Cases - Package Packing: Runs pnpm install and pnpm pack to produce a distributable tarball in the dist directory. - Consumer Verification: Installs the packed tarball alongside the local xdrs-core tarball in a consumer fixture, then runs mydevkit install, mydevkit check, and xdrs-core lint against the generated output. - Guided Publishing: Bumps the package version based on consumer impact and publishes only after local verification passes. - Use Case: After updating the mydevkit extension that composes xdrs-core through a standalone .filedistrc file, follow this Skill to confirm the packed tarball installs cleanly in a consumer workspace before publishing a new version. ## Quick Start Pack the mydevkit package, verify it installs and passes checks in the consumer fixture, then bump the version and publish.

Frequently Asked Questions about 001-release-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a pnpm packed package before publishing?▼

Run pnpm pack to produce a tarball, then install that tarball in a separate consumer workspace instead of publishing directly. Execute the package's CLI commands from the consumer to confirm the packed artifact works as consumers will use it.

How to test an XDRS extension package with a consumer workspace?▼

Install the packed mydevkit tarball together with the local xdrs-core tarball in the consumer fixture, then run mydevkit install and mydevkit check against the output directory. Finish by running xdrs-core lint on the generated output.

Does this release flow require pnpm?▼

Yes, the procedure relies on pnpm for dependency installation, packing with pnpm pack, and executing binaries through pnpm exec. Workspaces using npm or yarn would need equivalent pack and exec commands.

When should I bump the package version during release?▼

Bump the version according to the consumer impact of your changes, and only after the local consumer verification passes. Publishing before verification risks distributing a tarball that fails in downstream workspaces.

Why does consumer verification fail after packing?▼

Failures typically come from missing files in the packed tarball, incorrect .filedistrc composition, or version mismatches with the local xdrs-core package. Inspect the tarball contents and rerun the install and lint steps to isolate the failing phase.