/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,
One skill from brooks-lint.
shell
$ npx -y skills add hyhmrright/brooks-lint --skill brooks-audit --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/brooks-audit
Context preview
The summary Claude sees to decide when to auto-load this skill.
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,
Stats
Stars1,248
Forks59
LanguageJavaScript
LicenseMIT
Ships with brooks-lint
SKILL.md
brooks-audit.SKILL.md
--- 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. --- # Brooks-Lint — Architecture Audit ## 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
