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 Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Explicit invocation only: load solely when the user names it ("brooks-test" / "brooks test"). Never infer from generic test-quality or failing-test requests. 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.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- brooks-test
- description
- 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. Explicit invocation only: load solely when the user names it ("brooks-test" / "brooks test"). Never infer from generic test-quality or failing-test requests. 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.
02 资源文件 1
- 参考文档test-guide.md6.5 KB
03 SKILL.md 正文
Brooks-Lint — Test Quality Review
Setup
Read in order:
../_shared/common.md— Iron Law, Project Config, Report Template, Health Score../_shared/source-coverage.md— book coverage, exceptions, tradeoffs../_shared/test-decay-risks.md— test-space symptom definitions and sourcestest-guide.md(this directory) — the test quality review framework
Process
Scope: if the user did not share test files or point to a test directory, apply Auto
Scope Detection (../_shared/common.md) first.
- 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
04 同仓库更多 Skills
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
session-retro
Use at the end of meaningful work to capture lessons, follow-ups, and process improvements.
grilling
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
grill-me
A relentless interview to sharpen a plan or design.
dev-workflow
Use when making a non-trivial code, test, configuration, or documentation change that should be planned, implemented, and verified end-to-end.
code-review
Use when reviewing a change, pull request, diff, or patch for bugs, regressions, missing tests, and maintainability risks.