dsh-plugin-release

Validates DSH plugin packages for local, Git, or npm distribution readiness.

21|4|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/0xsline/dsh-spotlight --skill dsh-plugin-release-0xsline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dsh-plugin-release
Source: https://github.com/0xsline/dsh-spotlight/tree/main/.agents/skills/dsh-plugin-release
Command: npx skills add https://github.com/0xsline/dsh-spotlight --skill dsh-plugin-release-0xsline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a DSH plugin through a packed tarball, Git source, or npm registry involves many failure points: leftover template placeholders, broken prepare scripts, missing declaration files, and incomplete packed archives. This Skill provides a structured audit that proves a plugin artifact can actually be consumed through the chosen channel before any release happens. ## Core Features & Use Cases - Channel-specific validation: Checks packed local artifacts, Git-source installs with prepare scripts, and npm/tarball distributions against their distinct requirements. - Identity and portability audit: Greps for template markers, stale package names, absolute paths, credentials, and forbidden link:/file: dependencies across manifests and source. - Archive and consumer verification: Runs typecheck, tests, prepare, build, and pnpm pack dry-runs, then validates public exports by installing the tarball into a clean consumer. - Use Case: Before publishing a Cordis plugin, run this Skill to confirm the packed tarball contains every runtime and declaration file promised by package.json exports, and that a fresh Git clone installs and activates correctly in an isolated DSH profile. ## Quick Start Use the dsh-plugin-release skill to check whether this plugin is ready for Git and npm distribution without publishing it.

Frequently Asked Questions about dsh-plugin-release

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

FAQPage Schema
How do I check if my npm package is ready to publish?▼

Run the package's typecheck, tests, prepare, and build scripts, then inspect the archive with pnpm pack --dry-run --json. Verify that every file promised by main, types, and exports exists in the post-lifecycle file list, and install the tarball into a clean consumer to confirm public imports resolve.

How do I test a Git-based npm install before releasing?▼

Clone the repository into a clean directory and run the install so the package's prepare script executes using only the clone's reachable registry dependencies. Then verify every manifest-declared runtime and type entry loads, and test activation in an isolated DSH profile.

Why does pnpm pack miss TypeScript declaration files?▼

Packing runs lifecycle scripts including prepare before computing the archive, so declarations must be emitted by that lifecycle and not deleted afterward. If the dry-run file list omits promised .d.ts files, fix the prepare script so it emits declarations and bundles runtime files without removing them.

Can I use file: or link: dependencies in a published plugin?▼

No. Repository-relative link: and file: dependencies break Git and npm consumers because they resolve only on the original machine. All runtime dependencies must come from the registry and be declared in the package manifest and lockfile.

Does this release check publish the package to npm?▼

No. The Skill only validates distribution readiness and explicitly refuses to push, tag, create releases, or run registry publish commands without direct user authorization. Publication steps are reported as not performed unless separately approved.