/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
One skill from brooks-lint.
shell
$ npx -y skills add hyhmrright/brooks-lint --skill brooks-review --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/brooks-review
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
Stats
Stars1,248
Forks59
LanguageJavaScript
LicenseMIT
Ships with brooks-lint
SKILL.md
brooks-review.SKILL.md
--- name: brooks-review description: > 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. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared. --- # Brooks-Lint โ PR Review ## Setup 1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules 2. Read `../_shared/source-coverage.md` for book-level coverage, exceptions, and tradeoffs 3. Read `../_shared/decay-risks.md` for symptom definitions and source attributions 4. Read `pr-review-guide.md` in this directory for the analysis process ## Process **If the user has not specified files or pasted code:** apply Auto Scope Detection
