dsh-shipcheck
以证据为先的 DSH 前端发布检查：真实浏览器检查、用户流程、视觉基线和可复现报告。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:guo6x/dsh-shipcheck#17fd57f0921d142c25e48ebace5203083fb5b550Shipcheck 以 dsh-shipcheck 发布，当前版本为 0.4.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
· 中文说明 · DeepSeek Harness plugin
A frontend is not ready because an agent says “looks good”. It is ready when a real browser produces evidence.
dsh-shipcheck is an evidence-first frontend release checker for DeepSeek Harness. It uses dsh-pilot to open the real page, then produces deterministic checks, screenshots, named baselines, and reproducible JSON reports. It does not edit the project or auto-dismiss failures. Its evidence format is designed to accept higher-level design judgments from dsh-palate in the next integration phase.
Style libraries give an agent advice. Browser drivers give it hands. Shipcheck closes the delivery loop with facts first; a later palate integration can add design judgment without replacing the evidence:
project URL → real browser → page evidence → deterministic checks → baseline diff → report with screenshot
The first version checks:
Every failure includes concrete evidence. A baseline is only written by the explicit shipcheck_baseline tool; a normal run never changes the saved baseline.
| Tool | Purpose |
|---|---|
shipcheck_run | Inspect a URL in a real browser, run checks, compare a baseline, save a screenshot and JSON report |
shipcheck_matrix | Inspect 1-20 URLs as one release gate; keep route-level screenshots, reports, failures, and baselines |
shipcheck_flow | Execute a bounded user journey with real browser actions, step screenshots, assertions, and redacted evidence |
shipcheck_baseline | Explicitly capture a reviewed URL as a named structural baseline |
shipcheck_history | List recent reports and their pass/fail summaries |
The Web panel adds the same local-first flow: choose 单页, 多路由, or 流程, then inspect the status, failed checks, screenshots, and recent history.
dsh plugin --profile web add github:guo6x/dsh-pilot
dsh plugin --profile web add github:guo6x/dsh-shipcheck
Restart dsh web, open the 🚢 button in the sidebar, and paste a local URL such as http://127.0.0.1:3000.
For an agent-driven run, ask:
Run
shipcheck_runonhttp://127.0.0.1:3000as projectcheckout, require the visible textCheckout, forbidSomething went wrong, and tell me whether it is safe to continue manual review. Do not modify files.
After a human reviews a healthy page:
Capture the current checkout page as the
checkoutshipcheck baseline withshipcheck_baseline. Then runshipcheck_runagain and explain any structural regression with the evidence paths.
For a release with several important routes, ask:
Run
shipcheck_matrixforhttp://127.0.0.1:3000/,http://127.0.0.1:3000/login, andhttp://127.0.0.1:3000/checkoutas matrixcheckout-release. RequireCheckouton every route, forbidSomething went wrong, and report which route failed with its screenshot and JSON report path.
The matrix runs routes sequentially in one real browser session. Each route is saved as its own report and uses a generated baseline name under <matrix-name>/<route-key>, so the login page cannot overwrite the checkout page's baseline. The matrix report then aggregates all checks and includes a route-by-route summary.
For a real user journey, ask:
Run
shipcheck_flowfromhttp://127.0.0.1:3000/loginascheckout-login. Fill the Email and Password fields, click#submit, wait for the URL to include/dashboard, assert thatLogged inis visible, and tell me whether the journey passed. Do not modify files.
The flow tool accepts up to 30 ordered steps (navigate, click, fill, press, wait, wait_for, and assert). It captures evidence after every step and stops at the first failure. Filled values are used in the live browser but are replaced with [redacted] in the saved report. Clicking a submit button can still change the inspected application's state, so only provide explicit steps for an environment where that action is authorized.
The plugin stores local evidence under $DSH_HOME/shipcheck/:
shipcheck/
├── artifacts/ # screenshots
├── baselines/ # explicit named baselines
└── reports/ # recent JSON reports, capped at 100
A matrix therefore uses up to 21 report entries for 20 routes: one aggregate report plus one report per route.
No API key, cloud dashboard, embedding service, or automatic project write is required. dsh-pilot is a separate profile-level companion because DSH blocks GitHub repositories nested inside plugin dependencies; Shipcheck gives a clear error if it is missing.
pnpm install
pnpm test
The core tests use fake evidence and do not require a browser. The real browser path is exercised when shipcheck_run, shipcheck_matrix, or shipcheck_flow is used in a DSH Web profile.
MIT licensed.