lemonxiny55/dsh-lint-loop

Name: lemonxiny55/dsh-lint-loop
Author: lemonxiny55

Plugin插件 Native原生 ⭐ 3 MIT Dev Workflow开发与代码工作流

Zero-config lint feedback loop (eslint / biome / ruff) for DeepSeek Harness — lint_diagnostics / lint_workspace_errors / lint_fix tools plus an auto-injected post-edit findings section.

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-lint-loop is a zero-config, regression-aware lint repair plugin built specifically for DeepSeek Harness (dsh). After an Agent edit during a turn, the plugin batches and fixes only the lint regressions that were introduced or changed in files edited during that turn, deliberately ignoring pre-existing repository debt so the loop stays scoped to what the model actually broke. It exposes a small tool surface — lint_status, lint_repair, lint_diagnostics, lint_workspace_errors, and lint_fix — and shells out to whichever of eslint, biome, ruff, golangci-lint, or cargo clippy is already installed in the repo. No linter is bundled; binaries are resolved from node_modules/.bin first, then PATH, then linterPath, so installation is simply pnpm install plus whatever the host project already uses.

Typical usage is for dsh developers who want a model to clean up its own diff before the turn closes: call lint_diagnostics (or lint_repair for a batched one-pass fix) right after editing a file, then let the completion gate at agent/turn-stopping re-arm the turn if introduced or changed errors remain. The plugin captures a per-file lint baseline before each harness write, compares blocks of files actually touched this turn, and steers the agent for at most gateMaxSteers continuations (default 2) with an exact findings list — each file evaluated once per stopping, untouched files never block, and gate: false disables it entirely. Findings carry a source code frame with the offending line marked, so the model can patch without re-reading the file.

The plugin targets the dsh plugin surface only — README states it is not affiliated with DeepSeek — and lists a CI workflow plus vitest suite that runs against a marker-driven fake linter emitting real eslint 10 / biome 2.5 / ruff 0.16 JSON shapes, so no real linter is required in CI. pnpm build runs tsup and outputs dist/index.js as ESM with external dependencies. Known limits: ruff findings all surface as error (no severity); package-scoped linters analyze a whole package or crate; the harness rename event is not stable so deletes/renames are not eagerly migrated; auto-injection only observes harness-mediated writes; the harness itself is developer-preview with breaking API churn. License: MIT.

dsh-lint-loop 是一款面向 DeepSeek Harness (dsh) 的零配置回归感知 lint 修复插件，仅针对当前 Agent 回合内编辑的文件，批量修复由本次编辑引入或变更的 lint 问题，仓库既有瑕疵被忽略。它提供 lint_status、lint_repair、lint_diagnostics、lint_workspace_errors、lint_fix 等工具，可调用仓库自带的 eslint、biome、ruff、golangci-lint 或 cargo clippy，不内置任何 linter，二进制优先从 node_modules/.bin、PATH 或 linterPath 解析。

典型工作流是 Agent 编辑文件后调用 lint_diagnostics 或 lint_repair，工具会把引入项与历史项以 scope 字段区分，并在 agent/turn-stopping 钩子处执行完成门控：若被编辑文件仍有引入型或变更型错误未修复，则用具体诊断结果强制续写最多 gateMaxSteers 轮。它适合在 dsh 中希望自动化清理本轮引入 lint 回归的开发者，可避免会话被既有技术债阻塞。

依赖方面需用户自备 linter，pnpm install 后 pnpm test 通过 marker 驱动的假 linter 跑 vitest，无需真实工具，tsup 打包输出 ESM 的 dist/index.js。Ruff 无 severity 一律视为 error；golangci-lint 与 cargo clippy 走包/crate 范围，单文件 lint_fix 仅 diff 该文件；dsh 的 fs/observed 未暴露稳定的重命名事件，删除与重命名后需下一次调用重新解析路径；自动注入仅监听 harness 写入，外部编辑需工具调用触发；门控为有界续写而非硬阻断，最多两轮后放行回合。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-lint-loop（lemonxiny55/dsh-lint-loop）
仓库：https://github.com/lemonxiny55/dsh-lint-loop
本站详情页：https://www.yhbd.top/plugins/lemonxiny55-dsh-lint-loop/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 3 · 最近提交 2026-10-03 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意

Only 3 stars - very few users, little community feedback星标只有 3，几乎没人在用，遇到问题缺少社区反馈

DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装

npx @deepseek-ai/dsh plugin --profile web add dsh-lint-loop

把 lemonxiny55/dsh-lint-loop 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

19.2 KB · 缓存于 2026-09-29 05:49:27 · 19.2 KB

dsh-lint-loop

English | 中文

Using it? Tell us what works and what breaks — star the repo, ask a question, request a linter, or file an issue. Feedback directly shapes the roadmap.

Zero-config, regression-aware lint repair for DeepSeek Harness (dsh). After an Agent edit, lint_repair { scope: "turn" } batches and fixes only introduced or changed lint regressions in files edited during that turn. Existing repo debt is ignored. Uses the repo's eslint, biome, ruff, golangci-lint, or cargo clippy; no setup or bundled linters.

What the model gets

Tool	Purpose
`lint_status`	Compact current-turn summary: edited files, introduced/changed regressions, and historical findings ignored by repair.
`lint_repair`	Regression-aware self-repair — batches current-turn regressions by linter/package/crate, runs existing fixers, and re-lints for at most two rounds. Returns a repair receipt with found/fixed/remaining findings, affected files, fixer changes, and ignored pre-existing debt. Call after edits when you want one repair pass.
`lint_diagnostics`	Lint findings for one file (or all files the linters have seen), with rule, `file:line:col`, message, `scope` (`preexisting` / `introduced` / `changed`), and a `fixable` flag; severity, regression-scope, and `max` filters. Takes `file_path` (alias `file`). Call right after editing a file.
`lint_workspace_errors`	All current errors across files linted this session — including a `scope` label so historical debt is distinguishable from this turn's regressions.
`lint_fix`	Runs the repo's own fixer on one file and re-lints, returning changed lines, remaining and resolved findings, a baseline summary, and the linter used. `lint_repair` is the turn-wide regression-only option.

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 lemonxiny55/dsh-lint-loop 的 README.md。在 GitHub 查看原文 →