Brooks-Lint is a specialized skill designed for conducting thorough pull request (PR) code reviews. It focuses on identifying decay risks, design smells, and maintainability issues within code submissions. By leveraging a structured approach based on the Symptom → Source → Consequence → Remedy framework, this skill draws insights from twelve classic engineering books to provide actionable feedback. When you share code, a diff, or request a review, Brooks-Lint automatically triggers to analyze the provided material.

The review process begins with Auto Scope Detection, which helps define the context of the review. Once the scope is established, the skill systematically scans for decay risks, following a step-by-step guide. It includes a Quick Test Check to ensure that the code adheres to basic standards, although this step is skipped for documentation-only changes. The findings are then evaluated against the Iron Law, ensuring that each identified issue is contextualized and actionable.

This skill is particularly useful for developers and teams looking to maintain high code quality and prevent technical debt. By providing a clear report based on established engineering principles, Brooks-Lint helps teams understand not just what issues exist, but also the potential consequences and remedies for each finding. This makes it an invaluable tool for anyone involved in code review processes, from junior developers to seasoned architects.

To get started, users need to familiarize themselves with the setup instructions and the various shared resources that outline the analysis process, decay risks, and reporting templates. The skill is designed to integrate smoothly into existing workflows, ensuring that code reviews become more insightful and less error-prone.