DeepSeek Harness Plugin

zjukop3/dsh-vertical-kit#dsh-contributing-check

Category Docs & Rendering Added 2026-11-20

CONTRIBUTING-guide hygiene: a dev setup that can be followed, a test command that actually runs, what a pull request is expected to look like, the style the code is held to, where to ask, how commits should read, and whether a CLA or DCO applies. The test-command rule is the point: every guide says "make sure the tests pass"; the ones that work say `pnpm test`, and a guessed invocation is how a first PR arrives red. A file that only points at another guide is reported as a single pointer warning naming the target instead of being judged section by section. Measured on five public guides (nodejs/node, vitejs/vite, rust-lang/rust, kubernetes/kubernetes, django/django): vite passes clean, the other four are pointers. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:zjukop3/dsh-vertical-kit#path:/packages/dsh-contributing-check

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.