PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking...
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/brooks-review/SKILL.mdUse this skill when you need pR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking...
This is a self-contained local adaptation, not the complete upstream Brooks-Lint suite. Its shared configuration, source-coverage catalogue, risk taxonomy and numerical Health Score contract are not bundled. Do not load missing sibling skills or claim upstream grading compatibility, book-level coverage or an exact score.
Read pr-review-guide.md for the retained analysis process. Establish the user's diff or selected files using the actual repository and changed-file list; state any sampling. Use the named risks and evidence in that guide rather than invented upstream thresholds. A large diff or long function is a review lead, not by itself a demonstrated defect.
PR Review, scope, findings by severity, checks actually run, limits and next action. No findings is a valid result.BigSimmo/Communication
1120935
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.