Introduction

In DSH’s “everything is a plugin” model, a common engineering risk is premature agent assertions: claiming “I remember” without source evidence, “can execute” without a validated plan, “passed” without verified baseline results, or “safe” without completed release checks.

dsh-ops-kit is a DSH plugin package built around this issue: it provides a suite of capability bundles and tools for evidence-driven memory, orchestration planning, baseline operations, repository auditing, and plugin release processes for DSH profiles. Below is an introduction to its positioning, installation methods, core tools, and a few configuration points to note.

What is this

dsh-ops-kit is a reusable DeepSeek Harness bundle, maintained by LeslieWylie, under the MIT license.

It targets the DSH plugin ecosystem and addresses the core issue of ensuring agents ground their claims of “memory,” “plan,” “baseline results,” and “release safety” in verifiable evidence, checklists, or diagnostic results before asserting them. The documentation indicates it is conservative by default: it does not silently create issues, call remote APIs, start benchmarks, modify the repository, or read credentials.

Installation and Enablement

The official installation command is as follows:

dsh plugin --profile <profile> add dsh-ops-kit

Runtime requirements come from package.json engines:

node >=22.19.0

Since the plugin runs with the current DSH process permissions, it is recommended to check the source code, license, and commands like dsh-terminal-hotfix that perform hotfix actions before installation.

Core Capabilities

The following is the list of verified capability bundles/tools:

Tool Function
dsh_ops_capability_catalog List capability bundles included in the plugin package
dsh_ops_workflow_plan Generate scope → baseline → context → execute → verify → handoff plans
dsh_ops_skill_read Read the packaged full skill definition
dsh_ops_memory_search Search existing context in restricted local Markdown/code root directories and provide source evidence
dsh_ops_repository_audit Audit Git cleanliness, untracked files, and credential-path hygiene
dsh_ops_release_checklist Generate a complete DSH plugin release checklist
dsh_ops_plugin_doctor Check the plugin repository against the checklist
dsh_ops_runtime_doctor Check official terminal / persistent-bash prompt compatibility
dsh-terminal-hotfix Provide protected terminal prompt hotfix commands

Among them, dsh_ops_memory_search and dsh_ops_repository_audit are marked as read-only.

dsh_ops_release_checklist is used to generate the release checklist, while dsh_ops_plugin_doctor is used to check the plugin repository against the checklist. One focuses on “describing what is needed for release,” and the other focuses on “checking whether the plugin repository has achieved it.”

Local Roots Configuration

When using dsh_ops_memory_search or dsh_ops_repository_audit, it is recommended to configure roots as narrow directories, avoiding pointing to credential directories:

- id: dsh-ops-kit
  config:
    roots:
      - <project-root>
      - <memory-root>

If roots is not configured, the tool defaults to the DSH process working directory. The documentation states that credential-like paths and common run/secret directories will be rejected or skipped.

Verification and Terminal Prompt Hotfix

After installation or changes, you can run the following verification commands:

pnpm install --offline --ignore-scripts
pnpm build
pnpm typecheck
pnpm test

If there are compatibility issues between the official terminal and the persistent-bash prompt, check first before applying the hotfix:

dsh-terminal-hotfix --check
dsh-terminal-hotfix --apply

Restart DSH after applying. The documentation indicates that dsh-terminal-hotfix is not run by the plugin loader and does not silently edit dependencies.

Suitable Scenarios and Notes

Suitable for the following scenarios:

  1. When adding local context search to a DSH profile, you need source evidence instead of free-text recall.
  2. Before orchestrating research, multi-agent, baseline, or release tasks, you need a plan structure from scope to handoff.
  3. Before plugin release, you need to generate a release checklist and check the repository with the doctor.
  4. When troubleshooting terminal prompt handshakes or persistent-bash compatibility, you need read-only diagnostics and protected hotfix paths.

Notes:

  1. The plugin runs with the current DSH process permissions, so keep the roots configuration narrow when configuring.
  2. Do not point roots to credential directories.
  3. Default conservatism does not mean no manual review is needed; actions involving hotfixes and releases should still retain auditable records.
  4. Verified sources do not provide a confirmed directory page URL; when citing the directory entry, refer to the actual listing in the DSH community directory.

References

  • GitHub: https://github.com/LeslieWylie/dsh-ops-kit
  • Community Directory Page: Verified sources do not provide a fixed URL; search for dsh-ops-kit in the DSH community directory.