dsh-plugin-release

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing a DSH plugin without verification risks broken installs, missing declaration files, leaked credentials, or template placeholders reaching consumers. This Skill provides a structured audit that proves a plugin artifact actually works through its intended distribution channel before any release happens. ## Core Features & Use Cases - Channel-specific validation: Verifies packed local tarballs, Git-source installs with prepare scripts, and npm/tarball packages 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. - Full verification pipeline: Runs lockfile install, typecheck, tests, prepare, build, public export imports, and pnpm pack dry-run inspection of the post-lifecycle file list. - Use Case: Before publishing a Cordis-based DSH plugin to GitHub, run this Skill to confirm the prepare script builds declarations on a clean clone, the tarball contains every exported runtime file, and README install instructions match reality. ## Quick Start Use the dsh-plugin-release skill to check whether this plugin is ready for Git 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 verify a DSH plugin is ready for release?▼

Run the documented verification pipeline: install from the lockfile, then execute typecheck, tests, prepare, and build scripts. Inspect the packed archive with pnpm pack --dry-run --json and import every public export from lib/ under plain Node to confirm the artifact works.

How to test a plugin installs correctly from Git?▼

Test a clean clone or approved repository spec with no external source or configuration. The install must run the prepare script successfully using only the clone's reachable registry dependencies, then verify every manifest-declared runtime and type entry resolves.

What files should a pnpm plugin tarball contain?▼

The tarball must contain the runtime bundle, declarations and maps promised by exports, cordis.patch.yml for bundles, and any deliberately shipped assets. It must exclude credentials, .env, .git, node_modules, tests, and unexpected generated files.

Does this skill publish the plugin to npm?▼

No. The skill only validates distribution readiness and never changes remotes, pushes, tags, or runs registry publish commands without a direct user request. Publication actions are reported as not performed unless separately authorized.

Why does pnpm pack omit declaration files?▼

pnpm pack runs lifecycle scripts including prepare before calculating the archive, so the prepare script must recreate lib/ and emit declarations before bundling. If declarations promised by types or exports are missing, the package lifecycle itself needs fixing.