brooks-lint

What problem does it solve?

Standard linters and basic AI code reviewers only catch syntax errors and style violations, missing critical high-level design issues like tight coupling, missing abstractions, and architectural risks that accumulate as technical debt over time. This Skill fills that gap by reviewing code through the lens of 12 classic software engineering books to surface issues that would otherwise go unnoticed until they cause costly refactors or system failures.

Core Features & Use Cases

• Multi-lens code review: Evaluates code against principles from landmark engineering texts including Clean Code, The Pragmatic Programmer, Designing Data-Intensive Applications, and Domain-Driven Design.
• Targeted issue detection: Flags design smells, coupling violations, naming inconsistencies, missing stability patterns (timeouts, circuit breakers), and domain model clarity gaps.
• Use cases: Run before major refactors to identify structural debt, use when onboarding to a new codebase to map high-risk areas, or review code that functions correctly but feels architecturally misaligned.

Quick Start

Use the brooks-lint skill to review the PaymentService.ts file for design smells and coupling issues.