Brooks-Lint
FreeConduct thorough architecture audits with ease.
Free · Opens the source repo
What Brooks-Lint does
Brooks-Lint is a specialized skill designed for developers and architects who need to perform comprehensive architecture audits of their codebases. This skill systematically maps module dependencies, checks for layering integrity, and identifies structural decay, all while drawing on insights from twelve classic engineering texts. By leveraging this skill, users can gain a clearer understanding of their project's architecture and ensure that it adheres to best practices.
The audit process begins with context gathering, where the skill automatically detects the scope of the audit if none is specified. It then creates a module dependency graph using Mermaid, visually representing the relationships between different components of the codebase. Following this, Brooks-Lint scans for various decay risks, assigns colors to nodes in the graph based on the findings, and conducts assessments such as the Testability Seam Assessment and Conway's Law check. The final output is a structured report that highlights the findings, making it easy for users to identify areas that need attention.
This skill is particularly useful for teams undergoing code reviews, refactoring, or onboarding new developers. It provides a clear framework for understanding complex codebases and helps prevent issues that may arise from poor architectural decisions. By utilizing Brooks-Lint, teams can enhance their code quality and maintainability, ultimately leading to more robust software products.
When to use it
Use this skill when you need to audit your codebase's architecture, check for circular imports, or review module structures.
When not to use it
This skill is not suitable for tasks outside of architecture auditing or when specific environmental tests are required.
What you can build with it
Codebase Review Prior to Release
Use Brooks-Lint to perform a thorough audit of your codebase before a major release, ensuring all architectural concerns are addressed.
Onboarding New Developers
Leverage the onboarding mode of Brooks-Lint to help new developers understand the architecture of the codebase without diving into diagnostics.
Identifying Structural Issues
Run Brooks-Lint to identify and flag any structural decay or circular imports that may hinder code maintainability.
How to install Brooks-Lint
View source1. Install with the skills CLI
npx skills add sickn33/agentic-awesome-skills/brooks-audit --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by sickn33Brooks-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.mdfor the Iron Law, Project Config, Report Template, and Health Score rules - Read
../_shared/source-coverage.mdfor book-level coverage, exceptions, and tradeoffs - Read
../_shared/decay-risks.mdfor symptom definitions and source attributions - Read
architecture-guide.mdin 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.
Frequently asked questions about Brooks-Lint
Similar skills
Quality Playbook Generator
Run comprehensive quality audits on any codebase.
PR Draft Summary
Automate PR summary generation for openai-agents-python.
Final Release Review
Streamline your release candidate audits with ease.
Unit Test Vue Pinia
Efficiently write and review unit tests for Vue 3 applications.
Slang Shader Expert
Optimize and integrate Slang shaders with ease.
Telemetry Standards
Ensure consistent event tracking in Supabase Studio.