Plugin directory / Developer / dsh-plugin-workspace-rules
dsh-plugin-workspace-rules
Verified · install-tested on dsh youjiaqi421
What it does
Load Cursor, Gemini CLI, and GitHub Copilot workspace instructions into DeepSeek Harness.
Works — verified, early-stage project
Load Cursor, Gemini CLI, and GitHub Copilot workspace instructions into DeepSeek Harness. It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-plugin-workspace-rules
English | 锟斤拷锟斤拷
Load existing workspace instructions from Cursor, Gemini CLI, and GitHub Copilot into DeepSeek Harness.
The plugin reads these files from the workspace root, in order:
.cursorrulesGEMINI.md.github/copilot-instructions.md
Missing and empty files are ignored. Existing files are joined into one ordered system-prompt section and re-read before each model request, so edits apply without restarting Harness. Literal {{...}} text is preserved and is not interpreted as a Harness prompt variable.
Install from GitHub
Until an npm release is available, install the repository into a Harness profile:
dsh plugin --profile web add github:youjiaqi421/dsh-plugin-workspace-rules
pnpm 10 and newer block git dependency build scripts by default. If installation asks you to approve the package build, add the exact package key it reports to the profile's pnpm-workspace.yaml:
allowBuilds:
dsh-plugin-workspace-rules: true
Then repeat the install command. Allowing the build runs this repository's prepare script on your machine; review and pin the source commit when using it in a trusted setup.
Configure
The installed bundle works with no configuration. To override it, edit the profile's cordis.patch.yml:
- id: workspace-rules
config:
root: .
files:
- .cursorrules
- GEMINI.md
- .github/copilot-instructions.md
- docs/agent-rules.md
maxFileBytes: 65536
maxTotalBytes: 131072
order: 20
root is resolved from the directory where dsh starts. Every file path must be relative and remain inside that root. Duplicate paths, directories, invalid UTF-8, unreadable files, and size-limit violations fail loudly so the agent never runs with silently incomplete instructions.
Behavior
- File order is configuration order.
- Missing files and whitespace-only files contribute nothing.
- Files are decoded as strict UTF-8; a leading byte-order mark is removed.
maxFileByteslimits each source file.maxTotalByteslimits the complete rendered Markdown, including headings.- The prompt section defaults to order
20, after the deployment persona and before tool guidance. - Rule text is included in the request's recorded system prompt, preserving Harness replay behavior.
Develop
Requires Node.js ^22.19.0 || >=24 and pnpm.
pnpm install
pnpm run check
Install the checkout into a local profile from this directory:
dsh plugin --profile web add .
License
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install dsh-plugin-workspace-rules for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
This plugin is GitHub source (not published to npm) — install it straight from the repo:
Web profile:
dsh plugin --profile web add github:youjiaqi421/dsh-plugin-workspace-rules Headless (CLI) profile:
dsh plugin --profile headless add github:youjiaqi421/dsh-plugin-workspace-rules Test report
Verified: L1 install + L2 load + L3 runtime from GitHub source on dsh 0.1.0-rc.6.
When to use it
Extend the agent's coding surface — give it a new tool, workflow, or integration so it handles a dev task it couldn't before.
Who it's for
Developers who want dsh to behave like a teammate on real codebases — editing, running, and verifying changes rather than just answering.
For developers — extending it
The tool/command surface is the seam: expose more of the SDK, add smarter context wiring, or tighten the loop between code changes and verification.