Updated 4d ago
by hyhmrright
brooks-lint
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
1.5k GitHub stars (1,529)
+31 in 20 days
| Period | New stars |
|---|---|
| Sep 27 | 0 |
| Sep 28 | 0 |
| Sep 29 | +2 |
| Sep 30 | +1 |
| Oct 1 | 0 |
| Oct 2 | +2 |
| Oct 3 | −1 |
| Oct 4 | +1 |
| Oct 5 | +1 |
| Oct 6 | +1 |
| Oct 7 | +2 |
| Oct 8 | +3 |
| Oct 9 | +2 |
| Oct 10 | +1 |
| Oct 11 | 0 |
| Oct 12 | +1 |
| Oct 13 | +1 |
| Oct 14 | +4 |
| Oct 15 | +7 |
| Oct 16 | +3 |
- 9 skills (9 skills found in its SKILL.md files)
- 70 forks (70 forks)
- 4d ago last update (Last updated 4d ago)
Install
Skills CLI
npx skills add hyhmrright/brooks-lint
Asks which skills and agents to install. Just one: npx skills add hyhmrright/brooks-lint --skill brooks-audit — add -g for every project.
Claude Code
git clone https://github.com/hyhmrright/brooks-lintcp -r "brooks-lint/skills/brooks-audit" ~/.claude/skills/
Copies the brooks-audit skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add hyhmrright/brooks-lint
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on…
skills/brooks-audit/SKILL.md on GitHub (opens in a new tab) -
brooks-debt
Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT…
skills/brooks-debt/SKILL.md on GitHub (opens in a new tab) -
brooks-health
Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new…
skills/brooks-health/SKILL.md on GitHub (opens in a new tab) -
brooks-review
PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file.…
skills/brooks-review/SKILL.md on GitHub (opens in a new tab) -
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up t…
skills/brooks-sweep/SKILL.md on GitHub (opens in a new tab) -
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares te…
skills/brooks-test/SKILL.md on GitHub (opens in a new tab) -
brooks-harness
Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, cons…
.claude/skills/brooks-harness/SKILL.md on GitHub (opens in a new tab) -
new-skill
Scaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill"…
.claude/skills/new-skill/SKILL.md on GitHub (opens in a new tab) -
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NO…
.claude/skills/release/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.