Review code for design smells, coupling issues, and architectural risks.
npx skills add https://github.com/Avihusitton/gil-therapy --skill brooks-lint
Please help me install this Agent Skill. Skill: brooks-lint Source: https://github.com/Avihusitton/gil-therapy/tree/main/.agents/skills/brooks-lint Command: npx skills add https://github.com/Avihusitton/gil-therapy --skill brooks-lint
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.
Use the brooks-lint skill to review the PaymentService.ts file for design smells and coupling issues.
High-intent search queries and answers about installing and using this skill.
You can identify architectural flaws and design smells by reviewing code against principles from 12 classic software engineering books, targeting high-level coupling violations and structural debt that standard linters miss.
Yes, you can use AI to review code for coupling issues and DRY violations by applying principles from texts like Clean Code and Domain-Driven Design to surface architectural risks and domain model clarity gaps.
When onboarding to a legacy codebase, map high-risk areas by analyzing the code for missing stability patterns, architectural risks, and design smells to highlight structural debt before major refactors.
Yes, this approach catches missing fault tolerance patterns by evaluating code against domain-driven design rules and stability patterns, flagging missing circuit breakers and timeouts that could cause system failures.
The best way to analyze structural debt before refactoring is evaluating the codebase through a multi-lens review using landmark software engineering texts to identify violations of SRP and coupling issues.
High-level code review for architecture risks differs from standard linting by detecting missing abstractions and domain model clarity gaps, whereas standard tools only catch syntax errors and style violations.
wesleyegbertoApply SOLID, GRASP, and modularisation principles during code reviews.
lexicalninjaDetect architecture design issues and generate structured reports with file paths and priorities.
mymx2Parse SQL statements into a Concrete Syntax Tree preserving comments and whitespace.
DengNaichenAnalyze SwiftUI project architecture to detect anti-patterns and testability issues.
