---
name: Brooks Audit
slug: brooks-audit
category: Quality
description: Brooks Audit maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Use it for architecture audits or to give new developers a codebase tour.
github: "https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-audit"
language: JavaScript
stars: 1383
forks: 61
install: "npx degit https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-audit ~/.claude/skills/brooks-audit"
installs_to: ~/.claude/skills/brooks-audit
source_path: skills/brooks-audit/SKILL.md
collection_size: 9
category_size: 1354
collection_url: "https://dirskills.com/collections/hyhmrright/brooks-lint"
added: 2026-08-19T07:27:52.235Z
last_synced: 2026-08-19T07:27:52.235Z
canonical_url: "https://dirskills.com/skills/brooks-audit"
---

# Brooks Audit

Brooks Audit maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Use it for architecture audits or to give new developers a codebase tour.

**Install:**

```bash
npx degit https://github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-audit ~/.claude/skills/brooks-audit
```

## README

# 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`