brooks-health is a skill in hyhmrright/brooks-lint, last changed 20 Sept 2026. It is instructions only: no scripts, no named hosts and no pre-approved tools.

From the author
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 engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).

At a glance

What it can touch

  • Instructions only

It is instructions only: no scripts, no named hosts and no pre-approved tools.

How much a skill can do, not whether it is risky.

Pattern check

Nothing flagged

That isn't proof the skill is harmless.

Commit 85376e7 · 3 Nov 2026

How the check works

Pattern check: nothing flagged

That isn't proof the skill is harmless.

Install

Each tab says whether it installs commit 85376e7, the one we checked, or the latest version.

Read SKILL.md first
MIT
Licence
1.6k
Repo stars
Publisher
Files

What it can touch

From the files and frontmatter at commit 85376e7. This is how much a skill can do, not whether it is risky.

Instructions only

It is instructions only: no scripts, no named hosts and no pre-approved tools.

Pattern check

Pattern check: nothing flagged · commit 85376e7 · 3 Nov 2026

We checked every text file in this skill, at commit 85376e7 on 3 Nov 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

Format check

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

  • Agent Skills specPasses

    The open format from agentskills.io, held to the strictest version of each rule among the agents we check.

    • Note

      There is no license field, so readers can't tell whether they may reuse the skill. O2

      Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.

  • Claude CodePasses
  • Claude apps & API uploadPasses

    Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

    • Note

      The description is 753 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4

      Fix: If the claude.ai upload refuses it, trim the description to 200 characters.

  • OpenAI (Codex & API)Passes
  • VS Code & CopilotPasses

SKILL.md

Files

More from hyhmrright/brooks-lint

SkillWhat it can touchPattern checkLicenceUpdated
brooks-auditArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.
  • Instructions only

Pattern check: Nothing flaggedMITUpdated 20 Sept 2026

  • Instructions only
Pattern check: Nothing flaggedMIT20 Sept 2026
  • Instructions only
Pattern check: Nothing flaggedMIT20 Sept 2026
brooks-reviewPR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.
  • Instructions only

Pattern check: Nothing flaggedMITUpdated 20 Sept 2026

  • Instructions only
Pattern check: Nothing flaggedMIT20 Sept 2026
brooks-sweepFull-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. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. Do NOT trigger for: read-only audits or health reports where the user only wants findings without code changes; single-dimension reviews (use the focused skill instead: brooks-review / brooks-audit / brooks-debt / brooks-test); server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.
  • Runs shell commands

Pattern check: Nothing flaggedMITUpdated 15 Oct 2026

  • Runs shell commands
Pattern check: Nothing flaggedMIT15 Oct 2026
brooks-testTest 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.
  • Instructions only

Pattern check: Nothing flaggedMITUpdated 20 Sept 2026

  • Instructions only
Pattern check: Nothing flaggedMIT20 Sept 2026

Other Testing & QA skills

Same category, most repo stars first.

SkillWhat it can touchPattern checkLicenceUpdated
finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work

obra/superpowers

  • Runs shell commands
  • +1 more

Pattern check: Nothing flaggedMITUpdated 12 Aug 2026

  • Runs shell commands
  • Reaches the network
Pattern check: Nothing flaggedMIT12 Aug 2026
systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes

obra/superpowers

  • Runs shell commands
  • +1 more

Pattern check: Nothing flaggedMITUpdated 9 Oct 2026

  • Runs shell commands
  • Bundles scripts
Pattern check: Nothing flaggedMIT9 Oct 2026
  • Runs shell commands
  • Reaches the network
Pattern check: Nothing flaggedMIT10 Oct 2026
  • Instructions only
Pattern check: Nothing flaggedMIT11 Aug 2026
  • Runs shell commands
  • Reaches the network
  • +2 more
Pattern check: Nothing flaggedApache 2.020 Apr 2026
  • Instructions only
Pattern check: Nothing flaggedMIT8 Oct 2026

Repo facts from GitHub on 3 Nov 2026. Files read at commit 85376e7.

QAI did not write these skills and is not affiliated with their authors unless a page says so. Logos and icons belong to their owners and are not a mark of approval. How we check