Agent skill

Brooks Audit

by hyhmrright in 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.

MITAuto-check passedDevelopment

Install Brooks Audit

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

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

GitHub CLI
$ gh skill install hyhmrright/brooks-lint brooks-audit --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-audit .claude/skills/brooks-audit && 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-audit
GitHub stars
1.5k
Used in
1 other repo
Token cost
~537 tokens
SKILL.md length
187 words
Files
3
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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

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

What it does

Brooks Audit is an agent skill from 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. 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…

Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `architecture-guide.md` and `onboarding-guide.md`).

It sits in Development, covering Software architecture, Design patterns and Refactoring. It works with Mermaid. 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 to audit architecture
  • Review folder/module structure
  • Check for circular imports
  • Understand how the codebase is organized

Example prompts

  • “does this follow clean architecture?”
  • “why does everything depend on everything?”
  • “explain this codebase to a new developer”
  • “/brooks-audit”

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/decay-risks.md — symptom definitions and source attributions
  4. architecture-guide.md (this directory) — the audit 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 Audit loads about 537 tokens when it runs. Until then it costs about 185 tokens; SKILL.md has 187 words of instructions outside code blocks.

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

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). 187 words, ~537 tokens.

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

Brooks-Lint — Architecture Audit

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/decay-risks.md — symptom definitions and source attributions
  4. architecture-guide.md (this directory) — the audit framework

Process

Onboarding mode: If the user asks for an onboarding report, codebase tour, or "explain this codebase to a new developer", read onboarding-guide.md from this directory and follow it instead of architecture-guide.md. This mode explains rather than diagnoses — no Health Score, no Iron Law findings.

Scope: if the user did not specify files or a directory, apply Auto Scope Detection (../_shared/common.md) first.

  1. Gather codebase context and draw the module dependency graph as Mermaid (Steps 0–1 of the guide)
  2. Scan for each decay risk in the order specified (Steps 2–4 of the guide)
  3. Assign node colors in the Mermaid diagram based on findings (red/yellow/green) — after Step 4
  4. Run the Testability Seam Assessment (Step 5 of the guide)
  5. Run the Conway's Law check (Step 6 of the guide)
  6. Output using the Report Template from common.md — Mermaid graph FIRST, then Findings

Mode line in report: Architecture Audit

© 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 2 other files in skills/brooks-audit of hyhmrright/brooks-lint.

  • SKILL.md
  • architecture-guide.md
  • onboarding-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 Audit 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 Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brooks Audit this skillhyhmrright/brooks-lint1.5k1 repos~537Automated safety check: PassMIT
Architecture PatternsKartikLabhshetwar/better-shot2.4k2 repos~1.4kAutomated safety check: PassCustom licence
Pattern Conformance AuditTotoro-jam/battle-tested-patterns345—~1.6kAutomated safety check: PassMIT
Py Rigmudrii/hermesd118—~6.3kAutomated safety check: PassMIT
Component Design PrinciplesdavidYichengWei/agentic-engineering-framework158—~1kAutomated safety check: PassMIT
Uncle Bob Craftsickn33/agentic-awesome-skills47k2 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • Architecture Patterns

    KartikLabhshetwar/better-shot

    Deep dive into software architecture for macOS. An agent skill from KartikLabhshetwar/better-shot.

    2.4k GitHub starsUsed in 2 repos~1.4k tokens
    DevelopmentAuto-check passed
  • Pattern Conformance Audit

    Totoro-jam/battle-tested-patterns

    Audits a codebase's existing patterns, such as rate limiters, circuit breakers and caches, against canonical invariants and flags mislabeled or divergent ones.

    345 GitHub stars~1.6k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Py Rig

    mudrii/hermesd

    A skill your agent uses when building, reviewing, or refactoring Python code that requires strong maintainability discipline: SRP, DRY, OCP, explicit dependency injection, TDD/ATDD workflow, strict…

    118 GitHub stars~6.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Component Design Principles

    davidYichengWei/agentic-engineering-framework

    Chinese-language checklists for component-level design: class and module structure, public interfaces, data models, concurrency and error handling.

    158 GitHub stars~1k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed
  • Uncle Bob Craft

    sickn33/agentic-awesome-skills

    A skill your agent uses when performing code review, writing or refactoring code, or discussing architecture; complements clean-code and does not replace project linter/formatter.

    47k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Architecture Patterns

    secondsky/claude-skills

    Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

    227 GitHub starsUsed in 11 repos~2.4k tokens
    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 5 days ago
    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
  • Brooks Test

    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…

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

Works with

Categories

Questions about Brooks Audit

What does Brooks Audit do?

Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Brooks Audit is an agent skill from 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.

When should I use Brooks Audit?

Brooks Audit fits situations like: : user asks to audit architecture; review folder/module structure; check for circular imports; understand how the codebase is organized.

How do I install Brooks Audit in Claude Code?

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

How do I install Brooks Audit in Codex?

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

Can I use Brooks Audit 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-audit -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-audit, .gemini/skills/brooks-audit, .github/skills/brooks-audit and .opencode/skills/brooks-audit in your project.

What does Brooks Audit need to run?

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

Does Brooks Audit 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 Audit 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 Audit use?

Brooks Audit 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 Audit use?

About 537 tokens (SKILL.md is roughly 2.1k 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 Audit?

Skills that share tags, products or a category with Brooks Audit: Architecture Patterns (KartikLabhshetwar/better-shot, 2.4k stars), Pattern Conformance Audit (Totoro-jam/battle-tested-patterns, 345 stars), Py Rig (mudrii/hermesd, 118 stars) and Component Design Principles (davidYichengWei/agentic-engineering-framework, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brooks Audit?

hyhmrright (a GitHub user) maintains it in hyhmrright/brooks-lint, which has 1,513 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.