Brooks Review

Review existing code or diffs for maintainability, design decay, and architecture risks, reporting actionable Symptom → Source → Consequence → Remedy findings. Do not use for writing code from scratch.

neversight a06968c 2 files · 8.0 KB Updated

File contents

Brooks-Lint — PR Review

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

neversight/neverc/tree/main/.agents/skills/brooks-review commit a06968c830

Frequently asked questions

npx skillmds@latest add neversight/brooks-review