mcpbeat Sign in

Brooks Review Agent Skill

by hyhmrright

> 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. code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. questions, or framework/tool questions where no existing code is shared.

426 tokens
context cost
SKILL.md, read when the skill is used
2
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
1 313
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/hyhmrright/brooks-lint --skill brooks-review

What comes with it

6 991 bytes besides the instruction
pr-review-guide.md

The instruction itself

3 sections, as written by the author

Brooks-Lint — PR Review

Setup

Read in order:

  • ../_shared/common.md — Iron Law, Project Config, Report Template, Health Score
  • ../_shared/source-coverage.md — book coverage, exceptions, tradeoffs
  • ../_shared/decay-risks.md — symptom definitions and source attributions
  • pr-review-guide.md (this directory) — the analysis process

Process

Scope: if the user did not specify files or paste code, apply Auto Scope Detection

(../_shared/common.md) first.

  • 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
  • Apply the Iron Law to every finding
  • Output using the Report Template from common.md

Mode line in report: PR Review

How to use it

Copy the folder

Take hyhmrright/brooks-review from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.