Is Brooks Test safe and trustworthy?

tashan scores Brooks Test on public evidence — see the measured signals. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Brooks Test?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Brooks Test?

source: hyhmrright/brooks-lint.

‹ The Index

Brooks Test

skill

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.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Dev Tools & CI — see all ranked ›

Install (Claude Code):

cp -r brooks-test ~/.claude/skills/

Adoption: 1 repos

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

source ↗ · skill:hyhmrright/brooks-test

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-05 · scorer s5 · how · something wrong here?