RRepoGEO

REPOGEO REPORT · LITE

millionco/react-doctor

Default branch main · commit 8a3a1bee · scanned 5/16/2026, 2:07:29 AM

GitHub: 9,681 stars · 302 forks

AI VISIBILITY SCORE
33 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
2 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

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 millionco/react-doctor, 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.

OVERALL DIRECTION
  • highreadme#1
    Reposition README opening to explicitly state AI-generated code focus

    Why:

    CURRENT
    Your agent writes bad React, this catches it. One command scans your codebase and outputs a **0 to 100 health score** with actionable diagnostics. Works with Next.js, Vite, and React Native.
    COPY-PASTE FIX
    Your agent writes bad React. This catches it, providing a **0 to 100 health score** with actionable diagnostics specifically designed for AI-generated React code. Works with Next.js, Vite, and React Native.
  • hightopics#2
    Add specific AI-related topics

    Why:

    CURRENT
    agents, code-review, doctor, react, skill
    COPY-PASTE FIX
    agents, code-review, doctor, react, generative-ai, ai-code-review, code-quality, static-analysis
  • mediumreadme#3
    Elevate 'Install for your coding agent' section in README

    Why:

    CURRENT
    The 'Install for your coding agent' section appears after the general 'Install' section and a screenshot.
    COPY-PASTE FIX
    Move the 'Install for your coding agent' section to appear immediately after the initial problem statement and health score explanation, before the general `npx -y react-doctor@latest .` install instructions.

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.

Recall
0 / 2
0% of queries surface millionco/react-doctor
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
ESLint
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. ESLint · recommended 2×
  2. Webpack Bundle Analyzer · recommended 2×
  3. Prettier · recommended 1×
  4. React Developer Tools · recommended 1×
  5. Storybook · recommended 1×
  • CATEGORY QUERY
    How to review and improve React code quality generated by AI agents?
    you: not recommended
    AI recommended (in order):
    1. ESLint
    2. Prettier
    3. React Developer Tools
    4. Storybook
    5. React Testing Library
    6. Jest
    7. Webpack Bundle Analyzer
    8. Lighthouse

    AI recommended 8 alternatives but never named millionco/react-doctor. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools provide a health score and diagnostics for React application code?
    you: not recommended
    AI recommended (in order):
    1. SonarQube
    2. ESLint
    3. CodeClimate
    4. Snyk Code
    5. Bundlephobia
    6. Webpack Bundle Analyzer

    AI recommended 6 alternatives but never named millionco/react-doctor. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

  • README presence
    pass

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 millionco/react-doctor?
    pass
    AI named millionco/react-doctor explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts millionco/react-doctor in production, what risks or prerequisites should they evaluate first?
    pass
    AI named millionco/react-doctor 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 millionco/react-doctor solve, and who is the primary audience?
    pass
    AI did not name millionco/react-doctor — likely talking about a different project

    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 millionco/react-doctor. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/millionco/react-doctor.svg)](https://repogeo.com/en/r/millionco/react-doctor)
HTML
<a href="https://repogeo.com/en/r/millionco/react-doctor"><img src="https://repogeo.com/badge/millionco/react-doctor.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

millionco/react-doctor — 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