brooks-audit
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-
npx skills add hyhmrright/brooks-lint --skill brooks-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 th
- Setup
- Process
What does the brooks-audit skill do?
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-
How do I install it?
Run `npx skills add hyhmrright/brooks-lint --skill brooks-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hyhmrright/brooks-lint, a repository with 1,284 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.