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. 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.
How do I install this agent skill?
npx skills add https://github.com/hyhmrright/brooks-lint --skill brooks-reviewIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The Brooks-Lint skill is a structured code review tool that analyzes software changes for architectural decay and maintainability risks based on classic engineering principles. It is safe and does not contain any malicious code, unauthorized network requests, or sensitive file access patterns. The skill focuses entirely on text-based analysis and reporting within the agent's context.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Brooks-Lint — PR Review
Setup
- Read
../_shared/common.mdfor the Iron Law, Project Config, Report Template, and Health Score rules - Read
../_shared/source-coverage.mdfor book-level coverage, exceptions, and tradeoffs - Read
../_shared/decay-risks.mdfor symptom definitions and source attributions - Read
pr-review-guide.mdin 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
- Apply the Iron Law to every finding
- Output using the Report Template from common.md
Mode line in report: PR Review
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/hyhmrright/brooks-lint/brooks-review">View brooks-review on skillZs</a>