Agent skill · software engineering · sickn33
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.
Why this skill is useful
Provides domain-specific analysis patterns for code reviews that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Brooks-Lint — PR Review When to Use Use this skill when you need 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... 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 from ../shared/common.md to determine the review scope before proceeding. 1. Understand the review scope, then scan for each decay risk in the order specified (Steps 1–6 of the guide) 2. Run the Quick Test Check (Step 7 of the guide) — skip for docs-only or non-production changes 3. Apply the Iron Law to every finding 4. Output using the Report Template from common.md Mode line in report: PR Review Example User request: Use @brooks-review for this task: 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. Limitations Use this skill only when the task clearly matches its upstream source and local project context. Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes. Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/brooks-review--700e80