DSH Market
B

Brooks Lint

by hyhmrright · hyhmrright/brooks-lint

InstallableSkillcopy into placefresh

AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels, and 6 analysis modes including full-sweep auto-fix

Install Brooks Lint

Not a bundle: drop the SKILL.md directory into one of the skill roots DSH scans. No `dsh plugin add`, no build step.

This is a skill, not a bundle. Skills are not installed with dsh plugin add — a skill is a directory containing SKILL.md that DSH discovers by scanning its skill roots. Clone it into one of those roots and it is available on the next session.

Clone into your user skill root ($DSH_HOME/skills)

mkdir -p ~/.dsh/skills
git clone https://github.com/hyhmrright/brooks-lint.git ~/.dsh/skills/brooks-lint
RankRootPath
100project-dsh<project>/.dsh/skills
200project-agents<project>/.agents/skills
300customcustomSkillDirs in your config
400user-dsh$DSH_HOME/skills (default ~/.dsh/skills)
500user-agents$DSH_AGENTS_HOME/skills (default ~/.agents/skills)

Lower rank wins when two roots hold a skill with the same name. Put it in a project root instead of the user root when it should only apply to one repository.

Prerequisites

API key
Required — see the repository README for which provider.
Network access
Required at runtime.
Language
JavaScript

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checkedResultWeightWhat the spec says about it
lifecycleScriptspassinfono install-time scripts
entityTypepassinfoskill is not installed via `dsh plugin add`
Verdict reason
skill uses its own install path, so bundle checks do not apply
package.json read
package.json
Rules applied from
docs/user/develop/basic/publish.md
Checked at
2026-08-15

From the README

Excerpt as published by the author, plain text, unedited

Consistent. Traceable. Actionable. > *"The bearing of a child takes nine months, no matter how many women are assigned."* > — Frederick Brooks, *The Mythical Man-Month* (1975) **50 years later, Brooks was still right — and so were McConnell, Fowler, Martin, Hunt & Thomas, Evans, Ousterhout, Winters, Meszaros, Osherove, Feathers, and the Google Testing team.** Most code quality tools count lines and cyclomatic complexity. **brooks-lint** goes deeper — it diagnoses your code against six decay risk dimensions synthesized from twelve classic engineering books, producing structured findings with book citations, severity labels, and concrete remedies every time. For the full source-to-skill mapping, including exceptions and false-positive guards, see

Topics

GitHub topics on this repository

Related entries

Nearest entries by similarity — this one landed in no themed cluster