[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73FXGRMNKC19YVMD604R6E2":3,"skill-same:01M73FXGRMNKC19YVMD604R6E2":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M73FXGRMNKC19YVMD604R6E2","brooks-lint",null,"AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.","qhjqhj00\u002Fresearch-skills-pool","qhjqhj00","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29684092?v=4","01M72AE0ZGXVM5C57N512DGQG8","Tommy Chien","01M72AE107ESJMHT7QC5SXX144",3,"MIT","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fsickn33--antigravity-awesome-skills--skills__brooks-lint\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: brooks-lint\ndescription: \"AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.\"\ncategory: development\nrisk: safe\nsource: community\nsource_repo: hyhmrright\u002Fbrooks-lint\nsource_type: community\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Fbrooks-lint\u002Fblob\u002Fmain\u002FLICENSE\"\ndate_added: \"2026-04-29\"\nauthor: hyhmrright\ntags: [code-review, architecture, software-design, refactoring, claude-code]\ntools: [claude, codex, cursor, gemini]\n---\n\n# Brooks Lint\n\n## Overview\n\nBrooks Lint is a Claude Code skill that reviews your code through the lens of 12 classic software engineering books. Instead of checking style rules, it asks: \"What would the authors of *The Pragmatic Programmer*, *Clean Code*, and *Designing Data-Intensive Applications* say about this code?\"\n\nIt synthesizes the principles from landmark engineering books into actionable, structured feedback — catching design smells, tight coupling, missing abstractions, and architectural risks that linters and AI tools typically miss.\n\nNamed after Fred Brooks, author of *The Mythical Man-Month* — because the hardest bugs are conceptual, not syntactic.\n\n## The 12 Books\n\n| Book | Key Principles Applied |\n|------|----------------------|\n| *The Pragmatic Programmer* | DRY, orthogonality, tracer bullets |\n| *Clean Code* | Naming, function size, comment clarity |\n| *The Mythical Man-Month* | Conceptual integrity, second-system effect |\n| *Designing Data-Intensive Applications* | Data consistency, fault tolerance, scalability |\n| *A Philosophy of Software Design* | Deep modules, information hiding, complexity |\n| *Refactoring* | Code smells, extract method, encapsulation |\n| *Working Effectively with Legacy Code* | Seams, characterization tests, dependency breaking |\n| *Domain-Driven Design* | Ubiquitous language, bounded contexts, aggregates |\n| *Release It!* | Stability patterns, timeouts, bulkheads, circuit breakers |\n| *Structure and Interpretation of Computer Programs* | Abstraction, recursion, metalinguistic abstraction |\n| *The Art of UNIX Programming* | Modularity, composability, rule of least surprise |\n| *Extreme Programming Explained* | YAGNI, simple design, collective ownership |\n\n## When to Use This Skill\n\n- Use when you want architectural feedback beyond what linters provide\n- Use before major refactors to identify structural debt\n- Use when reviewing code that \"works but feels wrong\"\n- Use when onboarding to a codebase to quickly map risk areas\n- Use for design reviews before starting a new module or service\n\n## How It Works\n\nBrooks Lint applies each book's core principles as a review lens:\n\n1. **Smell detection**: Flags violations of DRY, SRP, Law of Demeter, etc.\n2. **Coupling analysis**: Identifies tight dependencies and missing abstraction layers\n3. **Naming critique**: Applies Clean Code naming rules to variables, methods, classes\n4. **Architecture review**: Checks for DDIA-style data consistency and fault tolerance gaps\n5. **Stability patterns**: Flags missing timeouts, retries, and circuit breakers (Release It!)\n6. **Complexity scoring**: Applies APOSD complexity metrics to identify over-engineered sections\n\n## Installation\n\n```bash\n# Install via Claude Code plugin marketplace\n# Search: \"brooks-lint\" in Claude Code > Extensions\n\n# Or install via NPX (Antigravity)\nnpx antigravity-awesome-skills --claude\n# Then invoke: @brooks-lint\n```\n\n## Examples\n\n### Example 1: Review a Service Class\n\n```\n@brooks-lint review src\u002Fservices\u002FPaymentService.ts\n```\n\n**Brooks Lint output:**\n```\n[Pragmatic Programmer] DRY violation: payment validation logic duplicated in 3 places\n[Clean Code] Method processPayment() does 4 things — violates Single Responsibility\n[Release It!] No timeout on external payment gateway call — risk of cascade failure\n[DDIA] No idempotency key — retry on network error will double-charge\n[APOSD] PaymentService knows too much about UserRepository — high coupling\n```\n\n### Example 2: Full Codebase Architecture Review\n\n```\n@brooks-lint analyze the overall architecture of this codebase\n```\n\n### Example 3: Pre-Refactor Review\n\n```\n@brooks-lint what are the biggest design smells in this module before I refactor it?\n```\n\n## Review Categories\n\n| Category | Books Applied | What It Catches |\n|----------|--------------|-----------------|\n| **DRY \u002F Duplication** | PP, Refactoring | Copy-paste code, shared logic not extracted |\n| **Naming** | Clean Code, DDD | Unclear names, domain language violations |\n| **Coupling** | APOSD, PP | Tight dependencies, missing interfaces |\n| **Stability** | Release It! | Missing timeouts, no retry logic, no circuit breakers |\n| **Data Integrity** | DDIA | Race conditions, non-idempotent operations |\n| **Complexity** | APOSD, SICP | Over-engineering, unnecessary abstraction |\n| **Legacy Debt** | WELC | Hard-to-test code, missing seams |\n| **Domain Clarity** | DDD, XP | Anemic models, missing bounded contexts |\n\n## Best Practices\n\n- Run `@brooks-lint` after writing new service layers or data pipelines\n- Combine with `@logic-lens` for full coverage: logic bugs + design smells\n- Use `@brooks-lint analyze architecture` weekly on growing codebases\n- Focus on CRITICAL and HIGH findings first — LOW findings are style suggestions\n\n## Related Skills\n\n- `@logic-lens` — Complementary: catches logic bugs; brooks-lint catches design issues\n- `@security-auditor` — Specialized security-only deep scan\n- `@lint-and-validate` — Style\u002Fsyntax linting to run alongside design review\n\n## Additional Resources\n\n- [GitHub Repository](https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Fbrooks-lint)\n- [Dev.to Article: I Synthesized 12 Classic Engineering Books into an AI Code Reviewer](https:\u002F\u002Fdev.to\u002Fhyhmrright\u002Fi-synthesized-12-classic-engineering-books-into-an-ai-code-reviewer-heres-what-it-caught-3ed1)\n- [Related skill: logic-lens](https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens)\n\n## Limitations\n\nUse this skill only when the task clearly matches the scope described above (design review and architectural analysis). Brooks Lint applies AI-powered analysis grounded in established engineering principles. It should complement — not replace — human design review for production-critical decisions. Results reflect the principles of the 12 source books and may not apply to all architectural styles or domains.\n","# Brooks Lint\n\n## Overview\n\nBrooks Lint is a Claude Code skill that reviews your code through the lens of 12 classic software engineering books. Instead of checking style rules, it asks: \"What would the authors of *The Pragmatic Programmer*, *Clean Code*, and *Designing Data-Intensive Applications* say about this code?\"\n\nIt synthesizes the principles from landmark engineering books into actionable, structured feedback — catching design smells, tight coupling, missing abstractions, and architectural risks that linters and AI tools typically miss.\n\nNamed after Fred Brooks, author of *The Mythical Man-Month* — because the hardest bugs are conceptual, not syntactic.\n\n## The 12 Books\n\n| Book | Key Principles Applied |\n|------|----------------------|\n| *The Pragmatic Programmer* | DRY, orthogonality, tracer bullets |\n| *Clean Code* | Naming, function size, comment clarity |\n| *The Mythical Man-Month* | Conceptual integrity, second-system effect |\n| *Designing Data-Intensive Applications* | Data consistency, fault tolerance, scalability |\n| *A Philosophy of Software Design* | Deep modules, information hiding, complexity |\n| *Refactoring* | Code smells, extract method, encapsulation |\n| *Working Effectively with Legacy Code* | Seams, characterization tests, dependency breaking |\n| *Domain-Driven Design* | Ubiquitous language, bounded contexts, aggregates |\n| *Release It!* | Stability patterns, timeouts, bulkheads, circuit breakers |\n| *Structure and Interpretation of Computer Programs* | Abstraction, recursion, metalinguistic abstraction |\n| *The Art of UNIX Programming* | Modularity, composability, rule of least surprise |\n| *Extreme Programming Explained* | YAGNI, simple design, collective ownership |\n\n## When to Use This Skill\n\n- Use when you want architectural feedback beyond what linters provide\n- Use before major refactors to identify structural debt\n- Use when reviewing code that \"works but feels wrong\"\n- Use when onboarding to a codebase to quickly map risk areas\n- Use for design reviews before starting a new module or service\n\n## How It Works\n\nBrooks Lint applies each book's core principles as a review lens:\n\n1. **Smell detection**: Flags violations of DRY, SRP, Law of Demeter, etc.\n2. **Coupling analysis**: Identifies tight dependencies and missing abstraction layers\n3. **Naming critique**: Applies Clean Code naming rules to variables, methods, classes\n4. **Architecture review**: Checks for DDIA-style data consistency and fault tolerance gaps\n5. **Stability patterns**: Flags missing timeouts, retries, and circuit breakers (Release It!)\n6. **Complexity scoring**: Applies APOSD complexity metrics to identify over-engineered sections\n\n## Installation\n\n```bash\n# Install via Claude Code plugin marketplace\n# Search: \"brooks-lint\" in Claude Code > Extensions\n\n# Or install via NPX (Antigravity)\nnpx antigravity-awesome-skills --claude\n# Then invoke: @brooks-lint\n```\n\n## Examples\n\n### Example 1: Review a Service Class\n\n```\n@brooks-lint review src\u002Fservices\u002FPaymentService.ts\n```\n\n**Brooks Lint output:**\n```\n[Pragmatic Programmer] DRY violation: payment validation logic duplicated in 3 places\n[Clean Code] Method processPayment() does 4 things — violates Single Responsibility\n[Release It!] No timeout on external payment gateway call — risk of cascade failure\n[DDIA] No idempotency key — retry on network error will double-charge\n[APOSD] PaymentService knows too much about UserRepository — high coupling\n```\n\n### Example 2: Full Codebase Architecture Review\n\n```\n@brooks-lint analyze the overall architecture of this codebase\n```\n\n### Example 3: Pre-Refactor Review\n\n```\n@brooks-lint what are the biggest design smells in this module before I refactor it?\n```\n\n## Review Categories\n\n| Category | Books Applied | What It Catches |\n|----------|--------------|-----------------|\n| **DRY \u002F Duplication** | PP, Refactoring | Copy-paste code, shared logic not extracted |\n| **Naming** | Clean Code, DDD | Unclear names, domain language violations |\n| **Coupling** | APOSD, PP | Tight dependencies, missing interfaces |\n| **Stability** | Release It! | Missing timeouts, no retry logic, no circuit breakers |\n| **Data Integrity** | DDIA | Race conditions, non-idempotent operations |\n| **Complexity** | APOSD, SICP | Over-engineering, unnecessary abstraction |\n| **Legacy Debt** | WELC | Hard-to-test code, missing seams |\n| **Domain Clarity** | DDD, XP | Anemic models, missing bounded contexts |\n\n## Best Practices\n\n- Run `@brooks-lint` after writing new service layers or data pipelines\n- Combine with `@logic-lens` for full coverage: logic bugs + design smells\n- Use `@brooks-lint analyze architecture` weekly on growing codebases\n- Focus on CRITICAL and HIGH findings first — LOW findings are style suggestions\n\n## Related Skills\n\n- `@logic-lens` — Complementary: catches logic bugs; brooks-lint catches design issues\n- `@security-auditor` — Specialized security-only deep scan\n- `@lint-and-validate` — Style\u002Fsyntax linting to run alongside design review\n\n## Additional Resources\n\n- [GitHub Repository](https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Fbrooks-lint)\n- [Dev.to Article: I Synthesized 12 Classic Engineering Books into an AI Code Reviewer](https:\u002F\u002Fdev.to\u002Fhyhmrright\u002Fi-synthesized-12-classic-engineering-books-into-an-ai-code-reviewer-heres-what-it-caught-3ed1)\n- [Related skill: logic-lens](https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens)\n\n## Limitations\n\nUse this skill only when the task clearly matches the scope described above (design review and architectural analysis). Brooks Lint applies AI-powered analysis grounded in established engineering principles. It should complement — not replace — human design review for production-critical decisions. Results reflect the principles of the 12 source books and may not apply to all architectural styles or domains.\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":36,"source":37,"license":15,"category":38,"date_added":39,"description":7,"source_repo":40,"source_type":37,"license_source":41},"safe",[26,27,28,29,30],"code-review","architecture","software-design","refactoring","claude-code",[32,33,34,35],"claude","codex","cursor","gemini","hyhmrright","community","development","2026-04-29","hyhmrright\u002Fbrooks-lint","https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Fbrooks-lint\u002Fblob\u002Fmain\u002FLICENSE","master","c247302c836de6438d746b45670990eb71691166","skills_collected\u002Fsickn33--antigravity-awesome-skills--skills__brooks-lint",1,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool","https:\u002F\u002Fgithub.com\u002Fqhjqhj00","chien.io","2026-05-11 15:07:59",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add qhjqhj00\u002Fresearch-skills-pool --skill brooks-lint",{"tool":56,"command":57},"bunx","bunx skills add qhjqhj00\u002Fresearch-skills-pool --skill brooks-lint",{"tool":59,"command":60},"pnpm","pnpm dlx skills add qhjqhj00\u002Fresearch-skills-pool --skill brooks-lint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fsickn33--antigravity-awesome-skills--skills__brooks-lint\u002FSKILL.md",true,[],[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M73JJB6EQPFPPVQK2Y9N67Q0","transformer-lens-interpretability","Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F130-transformer-lens\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M73JHTANRRWEE9HP98TPEHAY","wiki-vitepress","Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F126-wiki-vitepress\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M73JHJBMVFW46F1Y8K3SBF43","phoenix-observability","Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F124-phoenix\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M73JHFPA3A2806PMP42ZN86Q","frontend-ui-dark-ts","Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F123-frontend-ui-dark-ts\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M73JFVBVK57NRJS49TT2VDCT","tensorboard","Visualize training metrics, debug models with histograms, compare experiments, visualize model graphs, and profile performance with TensorBoard - Google's ML visualization toolkit","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F113-tensorboard\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M73JFF6PK6ZCN41C89J7HS2B","markdown-mermaid-writing","Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F110-markdown-mermaid-writing\u002FSKILL.md",[],[]]