exoticknight/dsh-plugin-template

This repository is a template project named dsh-plugin-template, maintained by exoticknight under the Apache-2.0 license, and it exists specifically to scaffold new plugins for DeepSeek Harness. The project already ships a full skeleton split into two entry points: a Host entry that runs inside DSH's Node process and is mounted as a Cordis plugin with a configuration schema, and a Client entry that is bundled into the format consumed by DSH's module loader. A --host-only flag strips out the client side for service-only plugins. The esbuild configuration treats every @deepseek-ai/* package as an external dependency supplied by DSH itself, injects the plugin name and version as build-time constants, and ships a bundle-manifest so the package can be picked up by the DSH runtime.

The intended workflow starts by clicking "Use this template" on GitHub or simply cloning the repo, then sending a single sentence in Chinese to a coding agent such as Claude Code, Codex, Cursor, or any other compatible programming assistant—for example, "用 dsh-plugin-template 建一个 DSH 插件 dsh-foo, 功能是……, 发布到 npm." From there the agent opens AGENTS.md and follows six numbered playbooks under playbooks/ that walk through 00-init (repo creation and parameter collection), 10-github (Actions permissions, tag protection, npm environment), 20-npm (Trusted Publisher, first publish), 30-release (tagging, recovery), 40-maintain (DSH and Node upgrades, Dependabot), and 50-listings (catalog submission plus README badge). The agent pauses only when human credentials are needed: npm login, the very first npm publish with its two-factor code, configuring the Trusted Publisher on npmjs.com, and approving the catalog submission.

Required tooling includes Node.js ^22.19.0 || >=24, pnpm, git, an authenticated GitHub CLI, and a DSH CLI for local testing; the manual path begins with node scripts/init.mjs --name dsh-foo --owner <user> --dsh-version <ver> --title "Foo" --description "Foo for DeepSeek Harness." followed by pnpm install, pnpm hooks:install, and pnpm verify. Development is kept isolated via pnpm dev, which links the current source into an in-repo .dsh-dev directory and verifies it never touches the user's regular DSH install, while pnpm smoke installs the already-published version into a throwaway directory and verifies it the same way end users would. CI runs on Ubuntu and Windows against Node 22.19 and 24, npm Trusted Publishing is preconfigured, GitHub Releases and notes are generated automatically, and prereleases flow through npm's next dist-tag. A first-run caveat is that AGENTS.md and playbooks/00-init.md must run before any plugin feature is written, otherwise template placeholders such as dsh-plugin-template, {{OWNER}}, and {{DSH_VERSION}} will survive into the published package.