Brooks Audit

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

.agents/skills/_shared

.agents/skills/brooks-audit

.agents/skills/brooks-debt

.agents/skills/brooks-health

.agents/skills/brooks-review

Audit 0.4.1 · source sha 8d83fdc82bd2 · 21 Oct 2026Report an issue or request a re-scan

• Publisherhyhmrright GitHub userOwner of the repository this skill is read from
• Source folderhyhmrright/brooks-lint/skills/brooks-auditThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict8d83fdc82bd2A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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,…

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

Excerpt, first 2,145 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/hyhmrright/brooks-lint
git -C brooks-lint checkout 8d83fdc82bd2

Works in

1. 2026-10-21
   !CAUTION B 89 / 100

   first audit · source 8d83fdc82bd2

Questions about Brooks Audit

• github.com/hyhmrright/brooks-lint/tree/main/skills/brooks-audit — the audited source at commit 8d83fdc82bd2 and every finding aboveObserved · 21 Oct 2026

Spotted something wrong? Report a correction · Methodology