dsh-plugins

dsh-plugins

Chinese documentation

A small pnpm monorepo for focused DeepSeek Harness plugins that do not need a repository of their own. Each package under plugins/ is an independently installable DSH bundle or native preset; see its installation instructions.

This README also catalogs klarkxy's public DSH plugins on npm, including packages maintained in other repositories. The browsable version is the plugin site. When a new plugin is published, add it to site/catalog.json and to both READMEs.

Plugins and presets

Package	Purpose	npm
@klarkxy/dsh-dev-index	DSH Docs: read official DSH docs in the Plugins page; Creator mode searches and fetches them with native tools.	npm
@klarkxy/dsh-pruner	Code Prune: review and simplify code while keeping existing behavior.	npm

Unpublished development packages

Package	Purpose	Status
@klarkxy/dsh-classmates	Teammate Roles: reusable teammate roles and native Team UI enhancements.	Local alpha; excluded from automatic npm publication and the plugin site.

Migrated from the local dsh-teammates directory. See the migration record.

Install published plugins from npm:

dsh plugin --profile web add @klarkxy/dsh-dev-index
dsh plugin --profile web add @klarkxy/dsh-pruner

Creator mode uses dsh_docs_search and dsh_docs_fetch from dsh-dev-index to read live official DSH documentation and verify runtime contracts.

Plugin site

https://klarkxy.github.io/dsh-plugins/ lists every plugin in Chinese and English, with a detail page per plugin: install commands in dependency order, the package README, requirements, and version history. It also publishes plugins.json and llms.txt for tools and agents.

site/catalog.json is the only hand-maintained part: slug, package, category, titles and summaries, README paths, and source repository. Versions, dates, dependencies, READMEs, and icons come from npm and jsDelivr at build time, so a release from another repository appears without a commit here.

pnpm site:build   # fetch live data and write _site/
pnpm site:test    # offline rendering tests, also part of pnpm check

.github/workflows/pages.yml builds and deploys _site/ on every main push, after each npm publish run, and once a day. If npm or jsDelivr cannot be reached the build fails and the previous deployment stays online. Pages → Source must be GitHub Actions. Old development-index URLs such as /areas/*.html redirect to the official DSH documentation.

Additional published plugins

Package names link to npm. Follow each plugin's documentation for installation, host compatibility, and configuration.

Package	Purpose	Documentation
@klarkxy/dsh-ai-services	AI Services: shared model routing, bounded auxiliary calls, and usage receipts.	Docs
@klarkxy/dsh-current-title	Auto Title: session titles follow the latest task; manual names stay put.	Docs
@klarkxy/dsh-fusion	Sidekick: persistent Lead–Sidekick collaboration with author-reviewed results.	Docs
@klarkxy/dsh-memory	Long-term Memory: scoped vocabulary, preferences, recent activity, and Dream consolidation.	Docs
@klarkxy/dsh-model-center	Model Center: configure model tiers, provider connections, and AI call limits.	Docs
@klarkxy/dsh-mood	Mood: proceed autonomously, ask only for genuine blockers, and summarize requirements on demand.	Docs
@klarkxy/dsh-recap	Session Recap: background recaps and bounded agent checkpoints.	Docs
@klarkxy/dsh-self-improvement	Experience Learning: learn conditional methods from outcome evidence, with optional skill export.	Docs
@klarkxy/dsh-web-search-manager	Web Search: manage web search providers and public-page fetching from one settings page.	Docs
@klarkxy/dsh-zhihu	Zhihu: Zhihu search, agent tools, knowledge bases, and usage tracking.	Docs
dsh-plugin-autoevo	Discover, review, and install reusable capabilities.	Docs

Development

Requires Node.js 24 or newer and pnpm 10.

pnpm install
pnpm check

Each package owns its assets, tests, and release version. Native presets need no runtime plugin or build. The repository root is not itself a DSH bundle.

Automatic npm releases

Every plugins/dsh-xxx package is named @klarkxy/dsh-xxx. Private development packages (private: true) participate in checks but are excluded from automatic releases. Public packages select the public npm registry. .github/workflows/npm-publish.yml checks packages on every main update. It can also be retried manually from Actions; release tags are not required.

After building, CI fingerprints the files selected by npm pack and compares them with the published package. Only changed packages or explicitly higher versions are published. Repository docs, the index website and tests excluded from the archive do not cause npm releases. Version fields and CI's own dshRelease.contentHash are excluded from the fingerprint to avoid release loops.

First releases keep the source version; an explicitly higher version takes precedence. Changed contents with no version increase get an automatic patch bump, or a prerelease counter bump for prereleases. CI updates package.json and any dsh.plugin.json, runs checks, publishes and verifies the archive, then commits the version back to main. Stable releases use latest; prereleases use next. Choose minor/major versions explicitly for new features or breaking changes; automatic patching does not replace compatibility judgment.

Publishing runs are serialized. Superseded commits are skipped and version writeback uses a normal fast-forward push, preserving concurrent commits. Bot commits do not recursively trigger workflows. Success requires the registry archive integrity to match the local archive. Retry failures from the latest main; unchanged packages already published successfully are skipped.

npm may scan packages before making them available. CI submits all changed packages first, then waits up to 20 minutes and verifies anonymous archive downloads. A timeout fails explicitly; retries recognize already accepted versions.

Use the repository Actions secret NPM_TOKEN for first publication. Then configure a Trusted Publisher per package: owner klarkxy, repository dsh-plugins, workflow npm-publish.yml, no environment, and direct publishing allowed. The token can then be removed. Version writeback needs the workflow's contents: write permission and branch rules that allow the bot to push to main.

License

SATA License 2.1

Editor public-plugin extraction

Ten portable packages are now maintained under plugins/, including Zhihu. Package names, tool behavior and persisted settings are unchanged; Zhihu now uses a local structural control adapter instead of a private UI dependency. Manuscript, proofread and application-private packages remain in Editor. Desktop preinstallation and offline startup are unchanged. See handoff and validation.