Skill

brooks-audit

Audits codebase architecture: maps module dependencies with Mermaid graphs, checks layering integrity, flags structural decay from 12 engineering books. For structure reviews, clean architecture checks, circular imports, and onboarding tours.

code-quality

npx claudepluginhub hyhmrright/brooks-lint --plugin brooks-lint

Tool Access

This skill uses the workspace's default tool permissions.

Preview

1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules

Supporting Assets

architecture-guide.mdonboarding-guide.md

SKILL.md

Similar Skills

deep-survey

Runs 7-phase analysis of TypeScript codebases using typegraph-mcp tools like ts_dependency_tree and ts_import_cycles, producing architectural report for onboarding or overviews.

typegraph

arch-review

Analyzes any codebase's architecture with 6 specialist agents (perf/scale, reliability, security, ops/DX, data/deps + Codex cross-review). Agents debate risks, fragile spots, improvements for audits/refactors.

1 file

arch-review

Code Architecture Review

Evaluates code architecture for maintainability and structural issues before they become technical debt. Use for PR reviews with changes, refactoring planning, new feature evaluation, debt assessment.

3 files

omer-metin-skills-for-antigravity-2

Stats

Stars95

Forks5

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Brooks-Lint — Architecture Audit

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

Brooks-Lint — Architecture Audit

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

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