brooks-audit
installsforks
How to install brooks-audit?
hyhmrright/brooks-lint/brooks-audit
$npx -y skills add hyhmrright/brooks-lint --skill brooks-auditArchitecture 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, unde
SKILL.md
| 1 | # Brooks-Lint — Architecture Audit |
| 2 | |
| 3 | ## Setup |
| 4 | |
| 5 | 1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules |
| 6 | 2. Read `../_shared/source-coverage.md` for book-level coverage, exceptions, and tradeoffs |
| 7 | 3. Read `../_shared/decay-risks.md` for symptom definitions and source attributions |
| 8 | 4. Read `architecture-guide.md` in this directory for the audit framework |
| 9 | |
| 10 | ## Process |
| 11 | |
| 12 | **Onboarding mode:** If the user asks for an onboarding report, codebase tour, or |
| 13 | "explain this codebase to a new developer", read `onboarding-guide.md` from this |
| 14 | directory and follow it instead of `architecture-guide.md`. This mode explains rather |
| 15 | than diagnoses — no Health Score, no Iron Law findings. |
| 16 | |
| 17 | **If the user has not specified files or a directory to audit:** apply Auto Scope |
| 18 | Detection from `../_shared/common.md` to determine the audit scope before proceeding. |
| 19 | |
| 20 | 1. Gather codebase context and draw the module dependency graph as Mermaid (Steps 0–1 of the guide) |
| 21 | 2. Scan for each decay risk in the order specified (Steps 2–4 of the guide) |
| 22 | 3. Assign node colors in the Mermaid diagram based on findings (red/yellow/green) — after Step 4 |
| 23 | 4. Run the Testability Seam Assessment (Step 5 of the guide) |
| 24 | 5. Run the Conway's Law check (Step 6 of the guide) |
| 25 | 6. Output using the Report Template from common.md — Mermaid graph FIRST, then Findings |
| 26 | |
| 27 | **Mode line in report:** `Architecture Audit` |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
