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.
Receba novas skills de Design e Frontend toda segunda
1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completaRecolher descrição
Brooks-Lint — PR Review
Setup
Read ../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules
Read ../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs
Read ../_shared/decay-risks.md for symptom definitions and source attributions
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 from ../_shared/common.md to determine the review scope before proceeding.
Understand the review scope, then scan for each decay risk in the order specified (Steps 1–6 of the guide)
Run the Quick Test Check (Step 7 of the guide) — skip for docs-only or non-production changes