Stats
Actions
Tags
From brooks-lint
Reviews PRs and code for decay risks, design smells, and maintainability issues using Symptom → Source → Consequence → Remedy findings from twelve classic engineering books.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brooks-lint:brooks-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules
../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs../_shared/decay-risks.md for symptom definitions and source attributionspr-review-guide.md in this directory for the analysis processIf the user has not specified files or pasted code: apply Auto Scope Detection
from ../_shared/common.md to determine the review scope before proceeding.
Mode line in report: PR Review
npx claudepluginhub hyhmrright/brooks-lint --plugin brooks-lintReviews code for design smells, tight coupling, missing abstractions, and architectural risks using principles from 12 classic software engineering books like Clean Code and The Pragmatic Programmer. Use before refactors, onboarding, or design reviews.
Performs production-level PR reviews using a consultant agent and 10-category framework prioritizing correctness, logic errors, type safety, and observability.
Systematically evaluates pull requests for correctness, design, readability, and tests, delivering actionable and kind feedback based on Google's engineering practices.