Uncle Bob Craft
sickn33/agentic-awesome-skills
A skill your agent uses when performing code review, writing or refactoring code, or discussing architecture; complements clean-code and does not replace project linter/formatter.
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.
Install Brooks Review
$ npx skills add hyhmrright/brooks-lint --skill brooks-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hyhmrright/brooks-lint brooks-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hyhmrright/brooks-lint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brooks-review .claude/skills/brooks-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "brooks-review" agent skill from https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-review into .claude/skills/brooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brooks-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hyhmrright/brooks-lint --skill brooks-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hyhmrright/brooks-lint brooks-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyhmrright/brooks-lint.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/brooks-review .agents/skills/brooks-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "brooks-review" agent skill from https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-review into .agents/skills/brooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brooks-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hyhmrright/brooks-lint --skill brooks-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hyhmrright/brooks-lint brooks-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyhmrright/brooks-lint.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/brooks-review .cursor/skills/brooks-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "brooks-review" agent skill from https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-review into .cursor/skills/brooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brooks-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hyhmrright/brooks-lint.git --path skills/brooks-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hyhmrright/brooks-lint --skill brooks-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hyhmrright/brooks-lint brooks-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyhmrright/brooks-lint.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/brooks-review .gemini/skills/brooks-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "brooks-review" agent skill from https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-review into .gemini/skills/brooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brooks-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hyhmrright/brooks-lint brooks-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hyhmrright/brooks-lint --skill brooks-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hyhmrright/brooks-lint.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/brooks-review .github/skills/brooks-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "brooks-review" agent skill from https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-review into .github/skills/brooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brooks-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hyhmrright/brooks-lint --skill brooks-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hyhmrright/brooks-lint brooks-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyhmrright/brooks-lint.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/brooks-review .opencode/skills/brooks-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "brooks-review" agent skill from https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-review into .opencode/skills/brooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brooks-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
brooks-review- GitHub stars
- 1.5k
- Used in
- 1 other repo
- Token cost
- ~430 tokens
- SKILL.md length
- 114 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 4 steps: ../_shared/common.md — Iron Law, Project… → ../_shared/source-coverage.md — book… → ../_shared/decay-risks.md — symptom… → …
- : user asks to review code
- SKILL.md covers Setup and Process
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Brooks Review is an agent skill from hyhmrright/brooks-lint. 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…
Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `pr-review-guide.md`).
It sits in Development, covering Design patterns, Refactoring and Code review. The repository describes itself as: AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels, and 6 analysis modes including full-sweep auto-fix. The licence is MIT.
When your agent uses it
- : user asks to review code
- Pastes code asking does this look right? / any issues here? / ready to merge?
- Asks for feedback on a function
- : questions about how to write code from scratch
Example prompts
- “does this look right?”
- “any issues here?”
- “ready to merge?”
- “/brooks-review”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- ../_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
What it can do on your machine
Read from SKILL.md and the folder at commit b6ef8a1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Brooks Review loads about 430 tokens when it runs. Until then it costs about 203 tokens; SKILL.md has 114 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hyhmrright/brooks-lint at commit b6ef8a1, republished under its MIT licence (© hyhmrright). 114 words, ~430 tokens.
Download SKILL.mdSave it as
.claude/skills/brooks-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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:
../_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 attributionspr-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
© hyhmrright, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/brooks-review of hyhmrright/brooks-lint.
- SKILL.md
- pr-review-guide.md
Open the folder on GitHubat commit b6ef8a1
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in hyhmrright/brooks-lint, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Brooks Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Brooks Review this skillhyhmrright/brooks-lint | 1.5k | 1 repos | ~430 | Automated safety check: Pass | MIT | |
| Uncle Bob Craftsickn33/agentic-awesome-skills | 47k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Expert Code ReviewerGulajavaMinistudio/Mayukai-Theme | 139 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Dignified Python Standardsdocling-project/docling | 69k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Clean Code GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Maintainable Code for iPolloWorkDevin-AXIS/iPolloWork | 6.8k | — | ~2.7k | Automated safety check: Pass | Custom licence |
Similar skills
Expert Code Reviewer
GulajavaMinistudio/Mayukai-Theme
Language-agnostic workflow for code reviews and security audits against Clean Code/SOLID principles, generating formal refactoring plans.
Dignified Python Standards
docling-project/docling
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
Clean Code Guard
amElnagdy/guard-skills
Reviews generated or changed production code against Clean Code, SOLID, DRY, KISS, YAGNI and LLM-specific failure modes before it ships, in any language.
Maintainable Code for iPolloWork
Devin-AXIS/iPolloWork
A code-change gate for the iPolloWork repository: search and reuse first, keep one source of truth, justify every new file or dependency, and audit the change.
Solid
ramziddin/solid-skills
A skill your agent uses when writing code, implementing features, refactoring, planning architecture, designing systems, reviewing code, or debugging.
More from hyhmrright/brooks-lint
Release
hyhmrright/brooks-lint
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG…
Brooks Audit
hyhmrright/brooks-lint
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books.
Brooks Debt
hyhmrright/brooks-lint
Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books.
Brooks Health
hyhmrright/brooks-lint
Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic…
Brooks Sweep
hyhmrright/brooks-lint
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase.
Brooks Test
hyhmrright/brooks-lint
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy…
Related
Categories
Questions about Brooks Review
What does Brooks Review do?
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. Brooks Review is an agent skill from hyhmrright/brooks-lint. 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.
When should I use Brooks Review?
Brooks Review fits situations like: : user asks to review code; pastes code asking does this look right? / any issues here? / ready to merge?; asks for feedback on a function; : questions about how to write code from scratch.
How do I install Brooks Review in Claude Code?
Run `npx skills add hyhmrright/brooks-lint --skill brooks-review -a claude-code`. Or copy the skill folder (skills/brooks-review in hyhmrright/brooks-lint) into .claude/skills/brooks-review in your project. Claude Code loads it when a task matches its description.
How do I install Brooks Review in Codex?
Run `npx skills add hyhmrright/brooks-lint --skill brooks-review -a codex`. Or copy the skill folder (skills/brooks-review in hyhmrright/brooks-lint) into .agents/skills/brooks-review in your project. Codex loads it when a task matches its description.
Can I use Brooks Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hyhmrright/brooks-lint --skill brooks-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brooks-review, .gemini/skills/brooks-review, .github/skills/brooks-review and .opencode/skills/brooks-review in your project.
What does Brooks Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Brooks Review is instructions for the agent only.
Does Brooks Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Brooks Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Brooks Review use?
Brooks Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Brooks Review use?
About 430 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Brooks Review?
Skills that share tags, products or a category with Brooks Review: Uncle Bob Craft (sickn33/agentic-awesome-skills, 47k stars), Expert Code Reviewer (GulajavaMinistudio/Mayukai-Theme, 139 stars), Dignified Python Standards (docling-project/docling, 69k stars) and Clean Code Guard (amElnagdy/guard-skills, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Brooks Review?
hyhmrright (a GitHub user) maintains it in hyhmrright/brooks-lint, which has 1,513 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.
Source: hyhmrright/brooks-lint on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.