Claude skill
Brooks Test
Brooks Test is a Claude skill in the Brooks Lint plugin. Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy…
What it does
The description in the skill's SKILL.md, which Claude reads to decide when to use it:
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.
The skill's instructions (about 120 words) cover:
- Setup
- Process
How to use it
- Brooks Test comes inside the Brooks Lint plugin, so you get it by installing that plugin, along with its 5 other skills. A plugin installs as one unit, with all its skills. The plugin's page has the install steps, and plugins are saved to your Claude account.
- Ask Claude for the task. When your request matches the skill's description, Claude loads it.
- To pick it yourself in Claude chat, type
/or click + and choose brooks-test. In Claude Code and Cowork, type:/brooks-lint:brooks-test
Source
- Plugin
- Brooks Lint
- SKILL.md
- View on GitHub
- Repo stars
- 1,578
- Repo last pushed
- Nov 16, 2026
- Checked
- Nov 16, 2026
More skills in Brooks Lint
- Brooks AuditArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books.
- Brooks DebtTech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books.
- Brooks HealthCombined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic…
- Brooks ReviewPR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books.
- Brooks SweepFull-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase.