REPOGEO REPORT · LITE
hyhmrright/brooks-lint
Default branch main · commit 8501ba44 · scanned 6/13/2026, 4:41:21 PM
GitHub: 1,033 stars · 48 forks
Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface hyhmrright/brooks-lint, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.
Action plan — copy-paste fixes
3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.
- highreadme#1Clarify the "Brooks" reference in the README's opening to prevent misinterpretation
Why:
CURRENT<h1 align="center">brooks-lint</h1> <p align="center"> <strong>AI code reviews grounded in twelve classic engineering books.<br> Consistent. Traceable. Actionable.</strong> </p>
COPY-PASTE FIX<h1 align="center">brooks-lint</h1> <p align="center"> <strong>AI code reviews grounded in the timeless wisdom of Frederick Brooks and twelve other classic engineering books.<br> Consistent. Traceable. Actionable.</strong> </p>
- mediumtopics#2Add more specific topics to improve category visibility
Why:
CURRENTai-code-review, architecture-review, auto-fix, claude-code-plugin, clean-architecture, code-health, code-quality, code-review, code-smells, codex-cli-plugin, developer-tools, gemini-cli-extension, github-actions, linting, llm, refactoring, software-design, software-engineering, tech-debt, test-quality
COPY-PASTE FIXai-code-review, architecture-review, auto-fix, claude-code-plugin, clean-architecture, code-health, code-quality, code-review, code-smells, codex-cli-plugin, developer-tools, gemini-cli-extension, github-actions, linting, llm, refactoring, software-design, software-engineering, tech-debt, test-quality, software-architecture-principles, design-patterns, engineering-best-practices, code-decay-diagnostics
- lowcomparison#3Add a "Comparison to other tools" section in the README
Why:
COPY-PASTE FIX## Comparison to other tools Unlike traditional linters and code quality platforms (e.g., SonarQube, DeepSource) that focus on metrics like cyclomatic complexity or code duplication, brooks-lint diagnoses code against established software engineering principles from classic books. We provide actionable findings with direct citations, focusing on architectural health and decay risks rather than just surface-level issues.
Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash
Category visibility — the real GEO test
Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?
Same questions for every model — switch tabs to compare answers and rankings.
- DeepSource · recommended 2×
- SonarQube · recommended 2×
- CodeGuru Reviewer (AWS) · recommended 1×
- Codiga · recommended 1×
- Kiuwan · recommended 1×
- CATEGORY QUERYHow can I get AI-powered code reviews focused on software design principles and architectural health?you: not recommendedAI recommended (in order):
- DeepSource
- SonarQube
- CodeGuru Reviewer (AWS)
- Codiga
- Kiuwan
- Semgrep
AI recommended 6 alternatives but never named hyhmrright/brooks-lint. This is the gap to close.
Show full AI answer
- CATEGORY QUERYWhat tools provide automated code quality analysis, identify tech debt, and offer auto-fix capabilities?you: not recommendedAI recommended (in order):
- SonarQube
- DeepSource
- CodeClimate
- Snyk Code
- ESLint
- Black
- Prettier
- Codacy
AI recommended 8 alternatives but never named hyhmrright/brooks-lint. This is the gap to close.
Show full AI answer
Objective checks
Rule-based audits of metadata signals AI engines weight most.
- Metadata completenesspass
- README presencepass
Self-mention check
Does AI even know your repo exists when asked about it directly?
- Compared to common alternatives in this category, what is the core differentiator of hyhmrright/brooks-lint?passAI named hyhmrright/brooks-lint explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
- If a team adopts hyhmrright/brooks-lint in production, what risks or prerequisites should they evaluate first?passAI named hyhmrright/brooks-lint explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
- In one sentence, what problem does the repo hyhmrright/brooks-lint solve, and who is the primary audience?passAI named hyhmrright/brooks-lint explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
Embed your GEO score
Drop this badge into the README of hyhmrright/brooks-lint. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.
[](https://repogeo.com/en/r/hyhmrright/brooks-lint)<a href="https://repogeo.com/en/r/hyhmrright/brooks-lint"><img src="https://repogeo.com/badge/hyhmrright/brooks-lint.svg" alt="RepoGEO" /></a>Subscribe to Pro for deep diagnoses
hyhmrright/brooks-lint — Lite scans stay free; this card itemizes Pro deep limits vs Lite.
- Deep reports10 / month
- Brand-free category queries5 vs 2 in Lite
- Prioritized action items8 vs 3 in Lite