agentleFS
MarvellbrazilMarvellbrazil/my-agentic-skills/skills/brooks-lint/SKILL.md

brooks-lint

Skill4 starsChanged 51 days agoMITView on GitHub

AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when you want architectural feedback beyond what linters provide

    line 46
  2. Distinctive:

    Use before major refactors to identify structural debt

    line 47
  3. Distinctive:

    Use when reviewing code that "works but feels wrong"

    line 48
  4. Distinctive:

    Use when onboarding to a codebase to quickly map risk areas

    line 49
  5. Distinctive:

    Use for design reviews before starting a new module or service

    line 50
  6. Very specific:

    Run @brooks-lint after writing new service layers or data pipelines

    line 118
  7. Very specific:

    Use @brooks-lint analyze architecture weekly on growing codebases

    line 120

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brooks Lint

Overview

Brooks Lint is a Claude Code skill that reviews your code through the lens of 12 classic software engineering books. Instead of checking style rules, it asks: "What would the authors of The Pragmatic Programmer, Clean Code, and Designing Data-Intensive Applications say about this code?"

It synthesizes the principles from landmark engineering books into actionable, structured feedback — catching design smells, tight coupling, missing abstractions, and architectural risks that linters and AI tools typically miss.

Named after Fred Brooks, author of The Mythical Man-Month — because the hardest bugs are conceptual, not syntactic.

The 12 Books

BookKey Principles Applied
The Pragmatic ProgrammerDRY, orthogonality, tracer bullets
Clean CodeNaming, function size, comment clarity
The Mythical Man-MonthConceptual integrity, second-system effect
Designing Data-Intensive ApplicationsData consistency, fault tolerance, scalability
A Philosophy of Software DesignDeep modules, information hiding, complexity
RefactoringCode smells, extract method, encapsulation
Working Effectively with Legacy CodeSeams, characterization tests, dependency breaking
Domain-Driven DesignUbiquitous language, bounded contexts, aggregates
Release It!Stability patterns, timeouts, bulkheads, circuit breakers
Structure and Interpretation of Computer ProgramsAbstraction, recursion, metalinguistic abstraction
The Art of UNIX ProgrammingModularity, composability, rule of least surprise
Extreme Programming ExplainedYAGNI, simple design, collective ownership

When to Use This Skill

  • Use when you want architectural feedback beyond what linters provide
  • Use before major refactors to identify structural debt
  • Use when reviewing code that "works but feels wrong"
  • Use when onboarding to a codebase to quickly map risk areas
  • Use for design reviews before starting a new module or service

How It Works

Brooks Lint applies each book's core principles as a review lens:

  1. Smell detection: Flags violations of DRY, SRP, Law of Demeter, etc.
  2. Coupling analysis: Identifies tight dependencies and missing abstraction layers
  3. Naming critique: Applies Clean Code naming rules to variables, methods, classes
  4. Architecture review: Checks for DDIA-style data consistency and fault tolerance gaps
  5. Stability patterns: Flags missing timeouts, retries, and circuit breakers (Release It!)
  6. Complexity scoring: Applies APOSD complexity metrics to identify over-engineered sections

Installation

# Install via Claude Code plugin marketplace
# Search: "brooks-lint" in Claude Code > Extensions

# Or install via NPX (Antigravity)
npx antigravity-awesome-skills --claude
# Then invoke: @brooks-lint

Examples

Example 1: Review a Service Class

@brooks-lint review src/services/PaymentService.ts

Brooks Lint output:

[Pragmatic Programmer] DRY violation: payment validation logic duplicated in 3 places
[Clean Code] Method processPayment() does 4 things — violates Single Responsibility
[Release It!] No timeout on external payment gateway call — risk of cascade failure
[DDIA] No idempotency key — retry on network error will double-charge
[APOSD] PaymentService knows too much about UserRepository — high coupling

Example 2: Full Codebase Architecture Review

@brooks-lint analyze the overall architecture of this codebase

Example 3: Pre-Refactor Review

@brooks-lint what are the biggest design smells in this module before I refactor it?

Review Categories

CategoryBooks AppliedWhat It Catches
DRY / DuplicationPP, RefactoringCopy-paste code, shared logic not extracted
NamingClean Code, DDDUnclear names, domain language violations
CouplingAPOSD, PPTight dependencies, missing interfaces
StabilityRelease It!Missing timeouts, no retry logic, no circuit breakers
Data IntegrityDDIARace conditions, non-idempotent operations
ComplexityAPOSD, SICPOver-engineering, unnecessary abstraction
Legacy DebtWELCHard-to-test code, missing seams
Domain ClarityDDD, XPAnemic models, missing bounded contexts

Best Practices

  • Run @brooks-lint after writing new service layers or data pipelines
  • Combine with @logic-lens for full coverage: logic bugs + design smells
  • Use @brooks-lint analyze architecture weekly on growing codebases
  • Focus on CRITICAL and HIGH findings first — LOW findings are style suggestions

Related Skills

  • @logic-lens — Complementary: catches logic bugs; brooks-lint catches design issues
  • @security-auditor — Specialized security-only deep scan
  • @lint-and-validate — Style/syntax linting to run alongside design review

Additional Resources

Limitations

Use this skill only when the task clearly matches the scope described above (design review and architectural analysis). Brooks Lint applies AI-powered analysis grounded in established engineering principles. It should complement — not replace — human design review for production-critical decisions. Results reflect the principles of the 12 source books and may not apply to all architectural styles or domains.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.