[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DD499RAYVHT33CS556FAQ9":3,"skill-same:01M7DD499RAYVHT33CS556FAQ9":66},{"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":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M7DD499RAYVHT33CS556FAQ9","brooks-lint",null,"AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.","Marvellbrazil\u002Fmy-agentic-skills","Marvellbrazil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184349613?v=4","01M7DCJPCRHP7SZS0T5H1GJZ8F","Marvello Faisal","01M7DCJPDCZDB94VG0QXGC6RC3",5,"MIT","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbrooks-lint\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","main","42203fde5eb692ba254e058168ee1af75855fcb4","skills\u002Fbrooks-lint",0,"https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills","skills.marvellofaisal.me","https:\u002F\u002Fgithub.com\u002FMarvellbrazil","marvellofaisal.me","Software Engineering Student | Backend & API Developer | Tech Enthusiast | Homelabber","2026-10-23 22:23:52",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Marvellbrazil\u002Fmy-agentic-skills --skill brooks-lint",{"tool":58,"command":59},"bunx","bunx skills add Marvellbrazil\u002Fmy-agentic-skills --skill brooks-lint",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Marvellbrazil\u002Fmy-agentic-skills --skill brooks-lint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbrooks-lint\u002FSKILL.md",true,[],[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DDQP2F4E42AMTGY0VCJ6G2","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DDQM00XGSGT8V797C89R2E","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DDQEF1HP9CMH88HMN9MCBA","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7DDQA32ZAG7J4PMRXRSQ3NQ","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7DDQ5482QSC0FC4NX107FVY","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7DDQ1GZ7Z2Y67460SJJEMC0","using-agent-skills","Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fusing-agent-skills\u002FSKILL.md",[],[]]