From brooks-lint
Reviews existing test suites for structural quality problems (brittleness, mock abuse, coverage illusions, slow execution, poor readability) drawing on classic engineering books.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brooks-lint:brooks-testThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules
../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs../_shared/test-decay-risks.md for test-space symptom definitions and source attributionstest-guide.md in this directory for the test quality review frameworkIf the user has not shared test files or pointed to a test directory: apply Auto
Scope Detection from ../_shared/common.md to determine the review scope before proceeding.
Mode line in report: Test Quality Review
npx claudepluginhub hyhmrright/brooks-lint --plugin brooks-lintReviews test files for bug-catching quality, grading on six dimensions like assertion depth, input coverage, mock health with actionable scorecard.
Enforces test quality principles including Arrange-Act-Assert structure, single behavior per test, and meaningful naming when writing or reviewing test code.
Reviews test coverage adequacy, test quality and assertions, and test architecture. Useful for evaluating testing strategy and ensuring test suite health.