dsh-compat

Usage

Inspect a local plugin without executing it:

node dist/cli.js inspect ./path/to/plugin
node dist/cli.js inspect ./path/to/plugin --format json
node dist/cli.js inspect ./path/to/plugin --strict

Generate a DSH bundle:

node dist/cli.js convert ./path/to/plugin --out ./generated-plugin
node dist/cli.js test ./generated-plugin

test currently performs deterministic static validation. It does not start source MCP/LSP servers or run source hooks.

Review the generated files before installing:

generated-plugin/
├── package.json
├── cordis.patch.yml
├── index.js
├── skills/
├── resources/
├── dsh-compat.env.example.json
├── dsh-compat.report.json
├── dsh-compat.report.md
├── dsh-compat.source-map.json
└── dsh-compat.lock.json

Then, at your discretion:

dsh plugin --profile 
 add -w ./generated-plugin
dsh --profile 
 --dump-config

MCP environment variables and HTTP headers are never copied with their values. Bind the names listed in dsh-compat.env.example.json through your reviewed DSH profile or generated patch before starting the MCP server.