> Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". or "give me a codebase tour" (use onboarding mode). questions — this skill analyzes structural/module-level concerns, not individual functions.
npx skills add https://github.com/hyhmrright/brooks-lint --skill brooks-audit
Read in order:
../_shared/common.md — Iron Law, Project Config, Report Template, Health Score../_shared/source-coverage.md — book coverage, exceptions, tradeoffs../_shared/decay-risks.md — symptom definitions and source attributionsarchitecture-guide.md (this directory) — the audit frameworkOnboarding 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.
Mode line in report: Architecture Audit
Take hyhmrright/brooks-audit from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.