Skip to content
  • Home
  • Plugin manual
  • dsh-plugin-check

omdsh-dev/dsh-plugin-check

210Last commit Aug 14, 2026

dsh-plugin-check DSH plugin

dsh-plugin-check scans plugin repositories for compliance with manifest protocol, patch format, build pitfalls, and hub inclusion. It outputs a compliance report with errors, warnings, and suggestions, without modifying the repository.

developer-toolsskills-workflows

How to install the dsh-plugin-check DSH plugin

dsh plugin --profile web add github:omdsh-dev/dsh-plugin-check

Copying does not run this command. Review the repository and version before installing the dsh-plugin-check DSH plugin.

dsh-plugin-check DSH plugin data source

dsh-plugin-check DSH plugin snapshot date: Aug 16, 2026

discovered

What the dsh-plugin-check DSH plugin can do

  • Checks manifest protocol (no-manifest, invalid-name, missing-main-or-types, no-patch, etc.)
  • Validates patch format (malformed-patch, patch-name-mismatch, duplicate-row-id, etc.)
  • Detects build traps (no-source-entry, no-tsconfig, missing-ts-ext-imports, lib-layout-mismatch, stale-ts-imports, etc.)
  • Evaluates ecosystem compliance (core-row-id, missing-profile-install-example, manual-install-only, core-modification-required)
  • Checks hub inclusion status (not-in-hub, hub-skipped as info)
  • Supports single check, recursive scan, and schema output modes

Where the dsh-plugin-check DSH plugin fits

  • Pre-submission self-check for DSH plugin authors
  • CI pipeline gate to automatically reject non-compliant plugin repositories
  • Batch scanning a directory of plugin repositories for compliance summary
  • Learning about common DSH plugin pitfalls and best practices

Who the dsh-plugin-check DSH plugin is for

  • DSH plugin authors and maintainers
  • CI/CD engineers integrating plugin quality gates
  • Plugin repository administrators

dsh-plugin-check DSH plugin limitations

  • Read-only: does not modify or build the checked repository
  • Build traps are detected by static text scanning, not by running tsc
  • Hub check requires local hub catalog (DSH_HUB_SOURCE or cwd/hub/) or GitHub API; silently degrades to skipped on failure
  • Only works on local file system paths (no remote repository URLs)

dsh-plugin-check DSH plugin: from the repository README

Quoted from the omdsh-dev/dsh-plugin-check README, the upstream source of the dsh-plugin-check DSH plugin. Copyright remains with the original authors.

DSH 插件健康检查工具 —— 扫描插件仓库，诊断**清单协议 / patch 格式 / 构建陷阱 / hub 收录状态**，输出合规报告与修复建议。**只读**，不修改、不构建被检查仓库。 [![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) ## 动机 组织内插件仓库持续增长，作者踩过的坑（cordis 双副本、tsconfig 三件套、patch name 不一致、产物 `.ts` 残留——运行时必崩）本可以自动化拦截。本工具把全部实测踩坑变成**可自动检查的门禁**：模型或 CI 直接对仓库目录跑一次 `plugin_check`，拿合规报告与修复建议。 ## 安全模型 - **只读**：仅 `readdir/stat/readFile`，绝不修改或构建被检查仓库 - **零业务依赖**：仅 node 内置模块（fs/path/child_process） - **hub 检查离线优先**：先读本地 hub catalog（`DSH_HUB_SOURCE` 或 cwd/hub/ 下），gh 调用作 fallback；全部失败静默降级 `skipped`（报告如实标注，不算警告） - **不执行 tsc**：构建陷阱全部静态文本扫描（快、无副作用） ## 工具声明 注册 `plugin_check` 工具（`@deepseek-ai/dsh-plugin-check`，row id `tool-plugin-check`），统一输出 JSON 文本。 | 参数 | 类型 | 必填 | 说明 | |---|---|---|---| | `action` | string | ✅ | `check` / `scan` / `schema` | | `path` | string | | 插件仓库目录（check）或父目录（scan）；默认当前工作目录 | | `strict` | boolean | | strict 模式：warning 升级为 error 影响 verdict，默认 false | ## Actions | action | 功能 | |---|---| | `check` | 检查单个插件仓库目录 → 合规报告（verdict/errors/warnings/suggestions） | | `scan` | 扫描父目录下所有 `dsh-*` 插件仓库（有 package.json 者）→ 汇总报告 | | `schema` | 输出全部检测项清单与判定标准（按形态适用的检测项矩阵，供模型/人核对） | ## 形态识别与检测项（按形态适用，33 项） | 类别 | error | warning | |---|---|-

Read the full READMERepository license: MIT

dsh-plugin-check DSH plugin questions

How do I install dsh-plugin-check?

You can install it via the DSH Profile Bundle command: `dsh plugin --profile web add github:omdsh-dev/dsh-plugin-check`. For headless profiles, use `dsh plugin --profile headless add github:omdsh-dev/dsh-plugin-check`. Alternatively, you can build locally and install with `npm pack` then `dsh plugin --profile <profile> add <tarball path>`.

What does the tool check?

It checks four categories: manifest protocol (e.g., missing manifest, invalid name, missing main/types), patch format (e.g., malformed patch, name mismatch, duplicate row id), build traps (e.g., no tsconfig, missing ts-ext imports, lib layout mismatch), and ecosystem compliance (e.g., core row id, missing profile install example, manual install only). It also checks hub inclusion status.

Is the tool safe to run on my plugin repository?

Yes, the tool is read-only. It only performs readdir, stat, and readFile operations. It does not modify or build the repository, and it does not execute tsc. All checks are static text scans.

Can I use this tool in CI?

Yes, it is designed for CI integration. You can run `plugin_check` with action `check` on a single repository or `scan` on a directory. The output is a JSON report that can be parsed by CI pipelines to enforce plugin quality gates.

How do I verify the installation?

After installation, run `dsh --profile <profile> --dump-config | grep tool-plugin-check` to confirm the plugin row is registered. Then test with a sample command like `dsh run "use plugin_check tool to check a plugin repository"`.