New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Brooks Test

by hyhmrright in hyhmrright/brooks-lint

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…

MITAuto-check passedDevelopment

Install Brooks Test

skills CLI
$ npx skills add hyhmrright/brooks-lint --skill brooks-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hyhmrright/brooks-lint brooks-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hyhmrright/brooks-lint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brooks-test .claude/skills/brooks-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
brooks-test
GitHub stars
1.5k
Used in
1 other repo
Token cost
~432 tokens
SKILL.md length
112 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 4 steps: ../_shared/common.md — Iron Law, Project… → ../_shared/source-coverage.md — book… → ../_shared/test-decay-risks.md —… → …
  • : user asks about test quality
  • SKILL.md covers Setup and Process
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Brooks Test is an agent skill from hyhmrright/brooks-lint. 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…

Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `test-guide.md`).

It sits in Development, covering Unit testing, Test generation and Legacy modernization. The repository describes itself as: AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels, and 6 analysis modes including full-sweep auto-fix. The licence is MIT.

When your agent uses it

  • : user asks about test quality
  • Shares test files for review
  • Expresses frustration: tests keep breaking whenever I change anything
  • Our tests take forever

Example prompts

  • “tests keep breaking whenever I change anything”
  • “our tests take forever”
  • “tests pass but bugs still reach production”
  • “/brooks-test”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. ../_shared/common.md — Iron Law, Project Config, Report Template, Health Score
  2. ../_shared/source-coverage.md — book coverage, exceptions, tradeoffs
  3. ../_shared/test-decay-risks.md — test-space symptom definitions and sources
  4. test-guide.md (this directory) — the test quality review framework

What it can do on your machine

Read from SKILL.md and the folder at commit b6ef8a1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Brooks Test loads about 432 tokens when it runs. Until then it costs about 210 tokens; SKILL.md has 112 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~210
When it runs · the whole SKILL.md, loaded when a task matches
~432

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hyhmrright/brooks-lint at commit b6ef8a1, republished under its MIT licence (© hyhmrright). 112 words, ~432 tokens.

Download SKILL.mdSave it as .claude/skills/brooks-test/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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. 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.
metadata.opencode/slash
true

Brooks-Lint — Test Quality Review

Setup

Read in order:

  1. ../_shared/common.md — Iron Law, Project Config, Report Template, Health Score
  2. ../_shared/source-coverage.md — book coverage, exceptions, tradeoffs
  3. ../_shared/test-decay-risks.md — test-space symptom definitions and sources
  4. 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.

  1. Build the test suite map (guide's "Before You Start" section)
  2. Scan for each test decay risk in the order specified (Steps 1–4 of the guide)
  3. Apply the Iron Law and output using the Report Template (Step 5 of the guide)

Mode line in report: Test Quality Review

© hyhmrright, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/brooks-test of hyhmrright/brooks-lint.

  • SKILL.md
  • test-guide.md

Open the folder on GitHubat commit b6ef8a1

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in hyhmrright/brooks-lint, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Brooks Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brooks Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brooks Test this skillhyhmrright/brooks-lint1.5k1 repos~432Automated safety check: PassMIT
Exp Test Maintainabilitydotnet/skills5.6k1 repos~2.5kAutomated safety check: PassMIT
MoAI TDD Workflowmodu-ai/moai-adk1.2k—~3.1kAutomated safety check: PassApache-2.0
Clean Codejd-solanki/slidev-theme-dracula1611 repos~3.8kAutomated safety check: PassMIT
Zizkadb TestZIZKA-AI-SL/ZizkaDB125—~358Automated safety check: PassCustom licence
Test Writer for Changed Codeposhan0126/dotclaude871—~1.2kAutomated safety check: PassMIT

Similar skills

  • Exp Test Maintainability

    dotnet/skills

    Official

    Detects duplicate boilerplate, copy-paste tests, and structural maintainability issues across .NET test suites.

    5.6k GitHub starsUsed in 1 repo~2.5k tokens
    DevelopmentAuto-check passed

  • MoAI TDD Workflow

    modu-ai/moai-adk

    Drives test-first development through the RED, GREEN, REFACTOR cycle, with a config switch that selects between TDD and a DDD workflow for existing code.

    1.2k GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Clean Code

    jd-solanki/slidev-theme-dracula

    Write readable, maintainable code through disciplined naming, small functions, and clean error handling.

    161 GitHub starsUsed in 1 repo~3.8k tokens
    DevelopmentAuto-check passed

  • Zizkadb Test

    ZIZKA-AI-SL/ZizkaDB

    Run the full ZizkaDB test suite across all layers — lint, Python unit tests, SDK tests, MCP tests, TypeScript tests, and dashboard build verification.

    125 GitHub stars~358 tokensUpdated 3 days ago
    Testing & QAAuto-check passed

  • Test Writer for Changed Code

    poshan0126/dotclaude

    Writes tests for newly added or changed code by reading the git diff, mapping every code path and writing one-assertion tests that match the project's conventions.

    871 GitHub stars~1.2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Code Explanation

    thalysjuvenal/advpl-specialist

    A skill your agent uses when the user asks to explain what a piece of ADVPL/TLPP code does in plain language, adapting the explanation depth for a junior developer (line-by-line), a senior developer…

    186 GitHub stars~488 tokensUpdated 25 days ago
    DevelopmentAuto-check passed

More from hyhmrright/brooks-lint

  • Release

    hyhmrright/brooks-lint

    Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG…

    1.5k GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed

  • Brooks Audit

    hyhmrright/brooks-lint

    Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books.

    1.5k GitHub starsUsed in 1 repo~537 tokens
    Auto-check passed

  • Brooks Debt

    hyhmrright/brooks-lint

    Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books.

    1.5k GitHub starsUsed in 1 repo~406 tokens
    Auto-check passed

  • Brooks Health

    hyhmrright/brooks-lint

    Combined 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…

    1.5k GitHub starsUsed in 1 repo~425 tokens
    Auto-check passed

  • Brooks Review

    hyhmrright/brooks-lint

    PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books.

    1.5k GitHub starsUsed in 1 repo~430 tokens
    Auto-check passed

  • Brooks Sweep

    hyhmrright/brooks-lint

    Full-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.

    1.5k GitHub starsUsed in 1 repo~508 tokens
    Auto-check passed

Categories

Questions about Brooks Test

What does Brooks Test do?

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…. Brooks Test is an agent skill from hyhmrright/brooks-lint. 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.

When should I use Brooks Test?

Brooks Test fits situations like: : user asks about test quality; shares test files for review; expresses frustration: tests keep breaking whenever I change anything; our tests take forever.

How do I install Brooks Test in Claude Code?

Run `npx skills add hyhmrright/brooks-lint --skill brooks-test -a claude-code`. Or copy the skill folder (skills/brooks-test in hyhmrright/brooks-lint) into .claude/skills/brooks-test in your project. Claude Code loads it when a task matches its description.

How do I install Brooks Test in Codex?

Run `npx skills add hyhmrright/brooks-lint --skill brooks-test -a codex`. Or copy the skill folder (skills/brooks-test in hyhmrright/brooks-lint) into .agents/skills/brooks-test in your project. Codex loads it when a task matches its description.

Can I use Brooks Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hyhmrright/brooks-lint --skill brooks-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brooks-test, .gemini/skills/brooks-test, .github/skills/brooks-test and .opencode/skills/brooks-test in your project.

What does Brooks Test need to run?

SKILL.md names no scripts, command-line tools or credentials: Brooks Test is instructions for the agent only.

Does Brooks Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Brooks Test safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Brooks Test use?

Brooks Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brooks Test use?

About 432 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Brooks Test?

Skills that share tags, products or a category with Brooks Test: Exp Test Maintainability (dotnet/skills, 5.6k stars), MoAI TDD Workflow (modu-ai/moai-adk, 1.2k stars), Clean Code (jd-solanki/slidev-theme-dracula, 161 stars) and Zizkadb Test (ZIZKA-AI-SL/ZizkaDB, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brooks Test?

hyhmrright (a GitHub user) maintains it in hyhmrright/brooks-lint, which has 1,512 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

Source: hyhmrright/brooks-lint on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.