brooks-lint — What is it?

brooks-lint is an AI-driven code review tool that diagnoses code decay risks using insights from classic engineering literature, providing actionable feedback and automated fixes.

⭐ 985 Stars 🍴 47 Forks JavaScript MIT Author: hyhmrright
Source: Official README and linked documentation View on GitHub →

Why it matters

brooks-lint is being discussed because its unique approach to code reviews, addressing the pain points of inconsistent and incomplete feedback from traditional tools. Its integration with Claude Code and Gemini CLI, along with its deep analysis based on classic engineering books, sets it apart in the market.

Source: Official README and linked documentation

Core Features

Decay Risk Diagnostics

Evaluates code against six decay risk dimensions, providing structured findings with book citations, severity labels, and concrete remedies.

Source: Official README and linked documentation
Analysis Modes

Supports six analysis modes, including full-sweep auto-fix, to address various code review needs.

Source: Official README and linked documentation
Book Citations

Incorporates insights from twelve classic engineering books, providing context and depth to the code review process.

Source: Official README and linked documentation

Architecture

The architecture of brooks-lint suggests a modular design with clear separation of concerns. It likely uses design patterns such as Dependency Injection for flexibility and maintainability. The code tree indicates a focus on CLI tools and integration with various platforms like Claude Code and Gemini CLI.

Source: Official repository tree and dependency files

Project Knowledge Graph

Knowledge graph: project (center) + core features (inner hexagons) + key dependencies (outer chips) @anthropic-ai/sdk@anthropic-ai/… Decay Risk DiagnosticsDecay Risk Diagnost… Analysis Modes Book Citations brooks-lint Project Core feature Key dependency

Tech Stack

LanguageJavaScriptFrameworkNot specified
@anthropic-ai/sdk
Not specified, but likely supports deployment on various platforms due to its integration with Claude Code and Gemini CLI.
Source: Official repository tree and dependency files

Quick Start

To install via Claude Code plugin marketplace: /plugin marketplace add hyhmrright/brooks-lint /plugin install brooks-lint@brooks-lint-marketplace To install manually: mkdir -p ~/.claude/skills/brooks-lint cp -r skills/* ~/.claude/skills/brooks-lint/ For Gemini CLI, use the extension installation command provided in the README.
Source: Official README and linked documentation

Use Cases

brooks-lint is suitable for developers and teams looking to improve code quality and maintainability. It is useful in scenarios such as PR reviews, architecture audits, tech debt assessments, and test quality reviews.

Source: Official README and linked documentation

Strengths & Limitations

Strengths

  • Provides in-depth code analysis with actionable feedback.
  • Integrates with popular coding platforms like Claude Code and Gemini CLI.
  • Grounded in classic engineering literature for context and depth.

Limitations

  • May have a steep learning curve due to its unique approach and features.
  • Dependency on external platforms for full functionality.
Source: Official README and linked documentation

Latest Release

v1.3.0 (2026-05-24): Added Codex marketplace icon and interface metadata. v1.2.3 (2026-05-13): Added script for version propagation. v1.2.2 (2026-04-29): Reduced skill token usage. v1.2.1 (2026-04-28): Fixed Codex CLI compatibility issue. v1.2.0 (2026-04-24): Introduced brooks-sweep with a sequential autonomous pipeline.

Source: Official releases

Verdict

brooks-lint is a tool for developers and teams aiming to enhance code quality and maintainability through a unique, AI-driven approach. Its integration with existing coding platforms and its deep analysis capabilities make it a valuable asset for those looking to improve their codebase's health and longevity.

Sources and review scope
This review is based on the project's public documentation. Versions, installation commands, and feature boundaries can change upstream; check the cited sources and current release before use. Sources checked on: 2026-09-23 13:55.

Reference materials: README, GitHub API, dependency files