AI Agent Hub
Back to plugins
⚙️

dsh-publish-skill

Workflow Updated 2026.08.17

Run the following command in DeepSeek Harness:

dsh plugin install WonderfulEdge/dsh-publish-skill

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install WonderfulEdge/dsh-publish-skill in the DeepSeek Harness terminal; the source repository is at https://github.com/WonderfulEdge/dsh-publish-skill. Restart the Web Harness process after installation to activate the plugin.

About this plugin

An XDSP frontend monorepo usually ships many packages, and a single release means running transpile and npm publish for each of them in a strict order, with no room for parallel execution. When one step fails, a human has to remember exactly where to resume. dsh-publish-skill folds that ritual into a single user-only /publish-skill command: you supply a target version, the plugin lists the modules that will ship, then runs yarn transpile and npm publish for each module strictly in sequence. If transpile finishes without errors the module is published immediately, so TypeScript type-checking noise no longer blocks the release.

Three granularities are available: publish every module under packages, resume from a specific START_PACKAGE after a failure, or publish a single PACKAGE in isolation. The plugin also updates the top-level version in each target module's package.json in one pass. It deliberately does not commit to Git, modify lockfiles, auto-login, or switch npm registries, leaving all side effects under human control. The skill is declared with disable-model-invocation, so the LLM will never select it on its own; the publishing flow only loads when the user types the command.

If your team maintains a multi-package XDSP frontend and needs a stable, resumable, auditable release pipeline, this plugin was built for exactly that job. It runs in the web profile, installs in seconds, and turns a repetitive script ritual into a single, human-gated workflow.

Use Cases

  • Sequentially publishing multiple npm packages from an XDSP frontend monorepo in a fixed order
  • Resuming the release pipeline from a specific module after a transpile failure
  • Shipping a single-module patch by updating its package.json version, then running transpile and publish in sequence

Best For

  • Frontend engineers maintaining multi-package XDSP frontend monorepos
  • Teams that need a stable, resumable, auditable sequential release pipeline
  • Developers using DeepSeek Harness as their daily environment and wanting CLI-triggered release workflows