Brooks Review

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

.agents/skills/_shared

.agents/skills/brooks-audit

.agents/skills/brooks-debt

.agents/skills/brooks-health

.agents/skills/brooks-review

Audit 0.4.1 · source sha e1648da16880 · 23 Oct 2026Report an issue or request a re-scan

• Publisherhyhmrright GitHub userOwner of the repository this skill is read from
• Source folderhyhmrright/brooks-lint/skills/brooks-reviewThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdicte1648da16880A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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…

---
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.
metadata:
  opencode/slash: "true"
---

# Brooks-Lint — PR Review

## Setup

Read in order:

1. `../_shared/common.md` — Iron Law, Project Config, Report Template, Health Score
2. `../_shared/source-coverage.md` — book coverage, exceptions, tradeoffs
3. `../_shared/decay-risks.md` — symptom definitions and source attributions
4. `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.

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`

Excerpt, first 1,718 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/hyhmrright/brooks-lint
git -C brooks-lint checkout e1648da16880

Works in

1. 2026-10-23
   !CAUTION B 89 / 100

   first audit · source e1648da16880

Questions about Brooks Review

• github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-review — the audited source at commit e1648da16880 and every finding aboveObserved · 23 Oct 2026

Spotted something wrong? Report a correction · Methodology