mcpbeat Sign in

Brooks Test Agent Skill

by hyhmrright

> 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 poor readability. take forever", "tests pass but bugs still reach production", or "we have too many mocks". workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.

427 tokens
context cost
SKILL.md, read when the skill is used
2
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
1 313
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/hyhmrright/brooks-lint --skill brooks-test

What comes with it

6 611 bytes besides the instruction
test-guide.md

The instruction itself

3 sections, as written by the author

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 sources
  • test-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

How to use it

Copy the folder

Take hyhmrright/brooks-test from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.