Agent skill · software engineering · sickn33
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books.
Why this skill is useful
Provides a structured framework for auditing architecture that includes specific checks for module dependencies and structural integrity, which the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Brooks-Lint — Architecture Audit When to Use Use this skill when you need 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... Setup 1. Read ../shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules 2. Read ../shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs 3. Read ../shared/decay-risks.md for symptom definitions and source attributions 4. Read architecture-guide.md in this directory for 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. If the user has not specified files or a directory to audit: apply Auto Scope Detection from ../shared/common.md to determine the audit scope before proceeding. 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 Limitations Use this skill only when the task clearly matches its upstream source and local project context. Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/brooks-audit