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.
In this repository144 other files it gives its agents.
- skills/composition-patterns/AGENTS.mdAGENTS.md
- skills/react-best-practices/AGENTS.mdAGENTS.md
- skills/react-native-skills/AGENTS.mdAGENTS.md
- antislop-codeSkill
- anti-slopSkill
- antislopSkill
- api-and-interface-designSkill
- api-endpoint-builderSkill
- astroSkill
- bddSkill
- brainstormSkill
- bring-me-ideasSkill
- browser-testing-with-devtoolsSkill
- cavemanSkill
- ci-cd-and-automationSkill
- cloudflareSkill
- codebase-audit-pre-pushSkill
- codebase-designSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- composition-patternsSkill
- constraint-driven-developmentSkill
- context7-mcpSkill
- context-engineeringSkill
- conventional-commitSkill
- conventional-commit-with-coauthorSkill
- credentialsSkill
- data-dummerSkill
- dddSkill
- debugging-and-error-recoverySkill
- deprecation-and-migrationSkill
- 3d-uiSkill
- ai-native-uiSkill
- aurora-uiSkill
- bento-uiSkill
- brutalismSkill
- brutalist-typographySkill
- card-based-designSkill
- claymorphismSkill
- color-blockingSkill
- command-center-uiSkill
- cyberpunk-uiSkill
- cyber-y2kSkill
- dark-modeSkill
- dashboard-designSkill
- data-dense-designSkill
- duotone-designSkill
- editorial-designSkill
- flat-design-2Skill
- flat-designSkill
- floating-uiSkill
- frutiger-aeroSkill
- glassmorphismSkill
- gradient-designSkill
- high-contrastSkill
- holographic-uiSkill
- isometric-designSkill
- layered-designSkill
- material-designSkill
- maximalismSkill
- The first 60 shown.
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
- Distinctive: line 46
Use when you want architectural feedback beyond what linters provide
- Distinctive: line 47
Use before major refactors to identify structural debt
- Distinctive: line 48
Use when reviewing code that "works but feels wrong"
- Distinctive: line 49
Use when onboarding to a codebase to quickly map risk areas
- Distinctive: line 50
Use for design reviews before starting a new module or service
- Very specific: line 118
Run @brooks-lint after writing new service layers or data pipelines
- Very specific: line 120
Use @brooks-lint analyze architecture weekly on growing codebases
≈ “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.
Files
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
| Book | Key Principles Applied |
| The Pragmatic Programmer | DRY, orthogonality, tracer bullets |
| Clean Code | Naming, function size, comment clarity |
| The Mythical Man-Month | Conceptual integrity, second-system effect |
| Designing Data-Intensive Applications | Data consistency, fault tolerance, scalability |
| A Philosophy of Software Design | Deep modules, information hiding, complexity |
| Refactoring | Code smells, extract method, encapsulation |
| Working Effectively with Legacy Code | Seams, characterization tests, dependency breaking |
| Domain-Driven Design | Ubiquitous language, bounded contexts, aggregates |
| Release It! | Stability patterns, timeouts, bulkheads, circuit breakers |
| Structure and Interpretation of Computer Programs | Abstraction, recursion, metalinguistic abstraction |
| The Art of UNIX Programming | Modularity, composability, rule of least surprise |
| Extreme Programming Explained | YAGNI, 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:
- Smell detection: Flags violations of DRY, SRP, Law of Demeter, etc.
- Coupling analysis: Identifies tight dependencies and missing abstraction layers
- Naming critique: Applies Clean Code naming rules to variables, methods, classes
- Architecture review: Checks for DDIA-style data consistency and fault tolerance gaps
- Stability patterns: Flags missing timeouts, retries, and circuit breakers (Release It!)
- 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-lintExamples
Example 1: Review a Service Class
@brooks-lint review src/services/PaymentService.tsBrooks 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 couplingExample 2: Full Codebase Architecture Review
@brooks-lint analyze the overall architecture of this codebaseExample 3: Pre-Refactor Review
@brooks-lint what are the biggest design smells in this module before I refactor it?Review Categories
| Category | Books Applied | What It Catches |
| DRY / Duplication | PP, Refactoring | Copy-paste code, shared logic not extracted |
| Naming | Clean Code, DDD | Unclear names, domain language violations |
| Coupling | APOSD, PP | Tight dependencies, missing interfaces |
| Stability | Release It! | Missing timeouts, no retry logic, no circuit breakers |
| Data Integrity | DDIA | Race conditions, non-idempotent operations |
| Complexity | APOSD, SICP | Over-engineering, unnecessary abstraction |
| Legacy Debt | WELC | Hard-to-test code, missing seams |
| Domain Clarity | DDD, XP | Anemic models, missing bounded contexts |
Best Practices
- Run
@brooks-lintafter writing new service layers or data pipelines - Combine with
@logic-lensfor full coverage: logic bugs + design smells - Use
@brooks-lint analyze architectureweekly 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
- GitHub Repository
- Dev.to Article: I Synthesized 12 Classic Engineering Books into an AI Code Reviewer
- Related skill: logic-lens
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.
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
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.

