How do I install the Brooks Audit skill?

Run npx skillmds@latest add lingxling/brooks-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Brooks Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Brooks Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Brooks Audit free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Brooks Audit?

lingxling (@lingxling) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Brooks Audit by lingxling — Agent Skill

Name: Brooks Audit
Rating: 4.2 (5 reviews)
Author: lingxling

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

lingxling Updated Sep 8, 2026 253 repo stars

File contents

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

Read ../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules
Read ../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs
Read ../_shared/decay-risks.md for symptom definitions and source attributions
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.

Gather codebase context and draw the module dependency graph as Mermaid (Steps 0–1 of the guide)
Scan for each decay risk in the order specified (Steps 2–4 of the guide)
Assign node colors in the Mermaid diagram based on findings (red/yellow/green) — after Step 4
Run the Testability Seam Assessment (Step 5 of the guide)
Run the Conway's Law check (Step 6 of the guide)
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.
Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

---name: brooks-auditdescription: 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...license: MIT---# Brooks-Lint — Architecture Audit## When to UseUse 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...## Setup1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules2. Read `../_shared/source-coverage.md` for book-level coverage, exceptions, and tradeoffs3. Read `../_shared/decay-risks.md` for symptom definitions and source attributions4. 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 thisdirectory and follow it instead of `architecture-guide.md`. This mode explains ratherthan diagnoses — no Health Score, no Iron Law findings.**If the user has not specified files or a directory to audit:** apply Auto ScopeDetection 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 44. 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.- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Frequently asked questions