What problem does it solve?
DeepSeek Harness (DSH) plugins can silently break when declarations mismatch artifacts, harness API references are outdated, or client bundles violate the module loader contract. This Skill provides a structured three-mode review workflow (design pre-check, quick review, formal acceptance) so plugin defects are caught before release instead of after deployment.
Core Features & Use Cases
- Mechanical Linting: Run scripts/lint.mjs against a plugin directory to check package.json declarations, dsh.bundle patch consistency, client artifact banner/footer contracts, and entry file existence, with exit code equal to the number of failures.
- Five-Layer Review Checklist: Covers mechanical checks, fact verification against harness source code, contract pitfalls (lossless JSON, DSL limits, subprocess handling, fail-loud semantics), documentation sync, and candidate-bound acceptance evidence.
- Formal Acceptance with Evidence Binding: Binds release verdicts to a specific commit, clean-profile installation, boot logs, and browser rendering screenshots, marking unverifiable items as NOT_VERIFIED.
- Use Case: Before publishing a DSH plugin with a browser client half, run the lint script for mechanical checks, trace every event/slot/API reference to harness source files, walk the ten contract pitfalls, and produce a quality report from the provided template.
Quick Start
Review the DSH plugin in the current directory with dsh-plugin-lint, starting with the mechanical lint script and then walking the fact and contract checklists.