code-architecture-review vs brooks-lint
code-architecture-review is a plugin bundle for AI coding tools published by Farjmand. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). brooks-lint is a plugin bundle for AI coding tools published by hyhmrright. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.4.3 Forks (GitHub): 69 Stars (GitHub): 1 517 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | code-architecture-review | brooks-lint |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 517 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 69 (better) |
| Last release | Not published | Not published |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | 1 | 13 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/farjmand/code-architecture-review | github.com/hyhmrright/brooks-lint |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
code-architecture-review
Drop this plugin into any project and ask Claude to "review my architecture." It scans for clean architecture violations, SOLID breaches, code smells, and structural anti-patterns across Node.js, Python, React, Go, and monorepo setups — then hands you a prioritized report with actionable fixes, not just vague warnings.
brooks-lint
Code quality diagnosis using principles from six classic software engineering books (The Mythical Man-Month, Clean Code, A Philosophy of Software Design, Working Effectively with Legacy Code, xUnit Test Patterns, The Art of Unit Testing). Surfaces decay risks across four review modes: PR Review, Architecture Audit, Tech Debt Assessment, and Test Quality Review. Every finding follows the Iron Law: Symptom → Source → Consequence → Remedy — grounding each issue in a named principle from the books.
How to run each
code-architecture-review As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install code-architecture-review@claude-community
brooks-lint As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install brooks-lint@claude-community
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: code-architecture-review · What it can do: brooks-lint · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.