Skills

brooks-review

brooks-review is a skill in hyhmrright/brooks-lint, last changed 20 Sept 2026. It is instructions only: no scripts, no named hosts and no pre-approved tools. Our pattern check flagged nothing at commit 15fa2d4 on 27 Oct 2026.

Pattern check: nothing flagged · commit 15fa2d4 · 27 Oct 2026

Install
From the author
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.
Licence
MIT
Repo stars
1.6k
Folder last changed
20 Sept 2026 (opens in a new tab)
Publisher
hyhmrright
Files
2 files
Checked
15fa2d4 (opens in a new tab) · 27 Oct 2026

Install

Each tab says whether it installs commit 15fa2d4, the one we checked, or the latest version.

No tab for your agent? Use Any agent for OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie, Amp and Antigravity, and Claude Code for Cline. Kiro needs the folder copied by hand.

Pinned to commit 15fa2d4, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/hyhmrright/brooks-lint.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin 15fa2d49877969f65a25b9f05897cd72fae32d33 &&
  git -C "$tmp" sparse-checkout set -- skills/brooks-review &&
  git -C "$tmp" checkout -q 15fa2d49877969f65a25b9f05897cd72fae32d33 &&
  mkdir -p .claude/skills &&
  mkdir .claude/skills/brooks-review &&
  cp -R "$tmp"/skills/brooks-review/. .claude/skills/brooks-review/ &&
  rm -rf "$tmp"

If Claude Code was already running and this created the skills folder, run /reload-skills.

Or install the brooks-lint plugin it ships in. Installs the latest version, not the one we checked. Installs everything in the plugin, including any hooks, MCP servers and scripts our check doesn't cover.

claude plugin marketplace add hyhmrright/brooks-lint --scope project &&
  claude plugin install brooks-lint@brooks-lint-marketplace --scope project
Claude Code docs (opens in a new tab)

What it can touch

From the files and frontmatter at commit 15fa2d4. This is how much a skill can do, not whether it is risky.

What it can touch: Instructions only

It is instructions only: no scripts, no named hosts and no pre-approved tools.

Pattern check

Pattern check: nothing flagged · commit 15fa2d4 · 27 Oct 2026

We checked every text file in this skill, at commit 15fa2d4 on 27 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

Format check

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

  • Agent Skills specPasses

    The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.

    • Note

      There is no license field, so readers can't tell whether they may reuse the skill. O2

      Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.

    • Note

      Reference files over 100 lines with no table of contents at the top: pr-review-guide.md (162 lines). B5

      Fix: Add a short list of the sections at the top of each.

  • Claude CodePasses

    Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.

    • Note

      Reference files over 100 lines with no table of contents at the top: pr-review-guide.md (162 lines). B5

      Fix: Add a short list of the sections at the top of each.

  • Claude apps & API uploadPasses

    Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

    • Note

      The description is 797 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4

      Fix: If the claude.ai upload refuses it, trim the description to 200 characters.

    • Note

      Reference files over 100 lines with no table of contents at the top: pr-review-guide.md (162 lines). B5

      Fix: Add a short list of the sections at the top of each.

  • OpenAI (Codex & API)Passes
  • VS Code & CopilotPasses

SKILL.md

Files

2 files

PathSize
SKILL.md (opens in a new tab)1.7 KB
pr-review-guide.md (opens in a new tab)6.8 KB

More from hyhmrright/brooks-lint

  • 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. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.

    • Instructions only
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 20 Sept 2026

  • 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. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.

    • Instructions only
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 20 Sept 2026

  • 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 engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).

    • Instructions only
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 20 Sept 2026

  • 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. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. Do NOT trigger for: read-only audits or health reports where the user only wants findings without code changes; single-dimension reviews (use the focused skill instead: brooks-review / brooks-audit / brooks-debt / brooks-test); server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.

    • Runs shell commands
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 15 Oct 2026

  • 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 Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.

    • Instructions only
    Pattern check: Nothing flagged

    MIT · 1.6k repo stars · Updated 20 Sept 2026