deepseekplugins

DeepSeek Harness plugin

dsh-tianshu-build

The shared dsh core as a profile bundle: every profile's first patch layer, inserting the base plugin rows over the empty profile root

Development & Runtime
Jump to install

Source facts

Repository
huiliyi37/oh-my-tianshu
Latest update
Aug 22, 2026
Category
Development & Runtime
GitHub stars
36
Format
plugin
Package path
packages/bundle/base
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
packages/bundle/base/package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/huiliyi37/oh-my-tianshu/tree/HEAD/packages/bundle/base
Plugin: dsh-tianshu-build
Author: huiliyi37

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer3 files
README.mdSource · read only
README language

@huiliyi37/dsh-base

English | 中文

The shared dsh core as a profile bundle: [cordis.patch.yml](cordis.patch.yml) inserts every base plugin row — model adapters, the shared [agent-default-model](../../core/agent-default-model/README.md) selection, tools, persistence, policy, settings/credentials, repository Plugins, telemetry — over the empty profile root, as the first layer of every profile's dsh.profile.bundles list. Later bundle layers (e.g. [dsh-web-app](../web-app/README.md)) and the user's profile cordis.patch.yml override these rows by id; a patch replaces a row's whole config, so mode-specific values live in mode bundles, not here. The package has no runtime API; the profile composer resolves the patch through the dsh.bundle.patch manifest field, never through code.

The base row for [/next-workflow](../../workflow/next-workflow/README.md) has no config, so every profile exposes the command once while package defaults keep verifyCommand unset. VERIFY reports unverified unless a later profile layer replaces the row with deployment-specific gate configuration.

The row set and its rationale are documented inline in the patch file; the [generated composition graph](../../../apps/cli/composition.md) renders it.

Model Experience

Indirectly, through the inserted rows: this bundle selects the shipped persona-less prompt base, tool set, and DeepSeek adapter that mode bundles specialize, and contributes no model-visible text of its own.

#### KV Cache effect

None directly; each inserted row's package owns its effect.

Known Limitations and Deferred Work

  • A patch replaces whole row configs — profile overrides must restate every field a row keeps; there is no deep-merge layer.
Back to searchOpen GitHub repository

More related plugins

View category