ben7am1n/dsh-lens-lite
Post-edit diagnostics for DeepSeek Harness
Post-edit diagnostics for DeepSeek Harness: after a file-mutating tool succeeds, the plugin runs the checkers you configured for that file's extension and attaches their output to the same tool result as model-visible context. The next model request already carries the type errors or lint findings the edit introduced, instead of the model discovering them a few turns later. Checkers are defined per extension with executable + arguments (e.g. tsc --noEmit, eslint --format compact) resolved against a scrubbed PATH.
Install
dsh plugin --profile web add dsh-lens-litedsh plugin --profile web add dsh-lens-lite (npm dsh-lens-lite 0.1.0, verified on npm 2026-08-30). Configure per-extension checker rows (name, extensions, argv) after install.
Compatibility
DSH web profile; Node.js; checkers run via subprocess provider (argv never shell-interpreted); MIT.
Details
- Repo: ben7am1n/dsh-lens-lite
- Category: Other
- Stars: 1
- Version: npm dsh-lens-lite 0.1.0
- Last push: 2026-08-13
- First seen: 2026-08-13
Recent updates
Runs per-extension checkers after file-mutating tools; output attached to the same tool result; tsc/eslint examples; argv never shell-interpreted.
FAQ
- When do checks run?
- After a file-mutating tool succeeds — the configured checkers for that file's extension run and their output is attached to the same tool result.
- How are checkers configured?
- Per extension with a required name, extensions list, and argv (executable + arguments, resolved against a scrubbed PATH, never shell-interpreted).
- Why is that useful?
- The next model request already carries the type errors/lint findings the edit introduced, instead of discovering them a few turns later.
Alternatives
ben7am1n/dsh-security-scan · ben7am1n/dsh-lens-lite · ben7am1n/dsh-lens-lite