hyhmrright/brooks-lint
Provides six code quality skills for code review, architecture audits, technical debt, test quality, health dashboards, and remediation.
Install
via npm
Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.
The desktop app keeps its own profile, desktop, and only the dsh command it ships may change it — the npm-installed dsh refuses that profile. Install the command from the app menu (Manage dsh Command…), open Desktop once, quit it fully, run the line below, then reopen Desktop.
via npm
Resolves a published tarball rather than cloning the repository.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/desktop/pnpm-workspace.yaml.
Our install check ran in a web profile on npm's dsh, not in the desktop app.
What happened when we ran it
Installed cleanly when we ran it
Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 6d agoon DeepSeek Harness 0.2.1-rc.5.
Show it in your README
For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.
Due diligence
Security
No build script was blocked in our run.
Source: our sandbox install on DeepSeek Harness 0.2.1-rc.5, 6d ago.
package.json declares no preinstall, install or postinstall script.
Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.
shell commands (bash, exec, spawn …)
Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.
Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.
What it is — Makes a DeepSeek Harness agent diagnose code against twelve engineering classics and return cited findings with remedies.
Who it is for — You already send living PRs, architecture slices, and test-debt through an agent in DeepSeek Harness, and you need conclusions tied to cognitive load, dependency direction, and domain distortion. A pipeline whose gates are the compiler and the test runner, and whose agent never opens existing design, will not absorb this.
Watch out — It installed on a fresh profile and harness registered it. It executes shell commands. The README we have is truncated, so the six commands’ exact boundaries are not fully verified here.
The verdict — I would put it on a repo I keep sending through review, not on a profile that only adds features.
Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.
brooks-lint is a DeepSeek Harness plugin that reviews code against six decay-risk dimensions derived from twelve classic software-engineering books. DeepSeek Harness loads brooks-lint as a skill, where the agent can use six named commands: /brooks-review, /brooks-audit, /brooks-debt, /brooks-test, /brooks-health, and /brooks-sweep. The commands analyse code and produce a 0–100 Health Score plus structured findings in the form Symptom → Source → Consequence → Remedy, with book citations, severity labels, and suggested remedies.
The checks cover cognitive overload, change propagation, knowledge duplication, accidental complexity, dependency disorder, and domain model distortion, alongside test-suite decay risks. This makes brooks-lint suitable for developers who want review and architecture discussions tied to named engineering principles rather than only line counts or cyclomatic complexity. The README does not document configuration keys, stored outputs, or files that brooks-lint writes; its documented output is the agent’s report.
brooks-lint is a poor fit when a project only needs conventional static metrics, or when its book-based diagnostic model is not wanted. The plugin is intended for Agent Skills-compatible environments and is installed into DeepSeek Harness with the web profile. Its detected terminal surface matters: installation and related workflows use shell commands, including a curl-piped installation script in the upstream README, so the agent’s terminal permissions should be considered before enabling it.
DeepSeek Harness exposes brooks-lint as an Agent Skills plugin. The agent applies its review skills to code and returns a 0–100 Health Score with findings structured as Symptom → Source → Consequence → Remedy. Each finding includes a book citation, a severity label, and a concrete remedy. The README does not describe a separate service, database, output file, or write operation.
The README documents six slash commands:
| Command | Purpose |
|---|---|
/brooks-review |
Code review |
/brooks-audit |
Architecture audit |
/brooks-debt |
Technical-debt analysis |
/brooks-test |
Test-quality analysis |
/brooks-health |
Health dashboard |
/brooks-sweep |
Remediation |
The commands can also be invoked through natural-language requests such as “review this PR” or “audit the architecture”, according to the README.
brooks-lint synthesises guidance from twelve classic engineering books. Its production-code checks cover Cognitive Overload, Change Propagation, Knowledge Duplication, Accidental Complexity, Dependency Disorder, and Domain Model Distortion. The README also describes six test-suite decay risks, although their individual names are not included in the supplied documentation.
DeepSeek Harness installs brooks-lint with the web profile. The upstream README identifies the package as an Agent Skills plugin and lists compatibility with platforms including Claude Code, Cursor, Codex, Gemini, Copilot, Windsurf, OpenCode, Kiro, and Bob. The supplied README excerpt documents no configuration keys, environment variables, version requirements, or project file requirements. brooks-lint has a terminal surface because its documented installation options include shell commands and a curl-piped script.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
zhu1090093659
Skill center for the dsh web GUI: browse all loaded skills grouped by source, enable or disable model invocation, create new skills, and delete into a recoverable trash.
Installed cleanly when we ran it
iflytek
Browse and search a SkillHub registry and manage local skill installation, updates, and removal inside DeepSeek Harness. Targets DSH 0.2.0-rc.2 and 0.2.1-rc.2; not yet compatible with 0.2.1-rc.3.
No one-line install — this plugin lives inside a larger repository and publishes no npm package.
chuspeeism
现代化可灵活嵌入的任务面板，支持 Codex、DeepSeek Harness
Installed cleanly when we ran it
QingYunA
Answers a question with a one-page visual HTML explainer: the model writes a short Markdown draft and the bundled `am` CLI builds the page, with flow, sequence, tree, timeline and ER diagrams, tables and callouts.
Installed cleanly when we ran it
Alisa0808
Turn one topic into a finished Vox-style paper-collage explainer/ad video — automated end to end on Atlas Cloud + ffmpeg. An agent skill.
Installed cleanly when we ran it
zhuyansen
Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.
Installed cleanly when we ran it
