Brooks test
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 CFrom its SKILL.md
npx -y skills add ranbot-ai/awesome-skills --skill brooks-testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.0 KB, 346 tokens by cl100k_base, as published. Nobody here has run it
Brooks-Lint — Test Quality Review
When to Use
Use this skill when you need 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...
Setup
- Read
../_shared/common.mdfor the Iron Law, Project Config, Report Template, and Health Score rules - Read
../_shared/source-coverage.mdfor book-level coverage, exceptions, and tradeoffs - Read
../_shared/test-decay-risks.mdfor test-space symptom definitions and source attributions - Read
test-guide.mdin this directory for the test quality review framework
Process
If 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.
- Build the test suite map (guide's "Before You Start" section)
- Scan for each test decay risk in the order specified (Steps 1–4 of the guide)
- Apply the Iron Law and output using the Report Template (Step 5 of the guide)
Mode line in report: Test Quality Review
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.