RRepoGEO

REPOGEO REPORT · LITE

nilbuild/diffity

Default branch main · commit d970fa28 · scanned 6/2/2026, 5:08:17 PM

GitHub: 686 stars · 36 forks

AI VISIBILITY SCORE
28 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 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 nilbuild/diffity, 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
  • hightopics#1
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    code-review, diff-viewer, ai-tools, github-style, developer-tools, cli, code-analysis
  • highreadme#2
    Reposition the README's core value proposition

    Why:

    CURRENT
    Diffity is an agent-agnostic, GitHub-style diff viewer and code review tool.
    COPY-PASTE FIX
    Diffity is an **AI-first, GitHub-style diff viewer and code review tool** for developers working with agents like Claude Code and Cursor.
  • mediumreadme#3
    Add a comparison section to the README

    Why:

    COPY-PASTE FIX
    Add a new section titled '## Diffity vs. Other Tools' or '## Why Diffity?' that highlights its unique strengths (e.g., agent-agnostic, local PR review, AI integration, guided tours) compared to generic diff tools or platform-specific code review solutions.

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 nilbuild/diffity
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GitHub Code Review
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. GitHub Code Review · recommended 1×
  2. GitHub Copilot · recommended 1×
  3. CodeQL · recommended 1×
  4. GitLab Code Review · recommended 1×
  5. GitLab Duo Code Suggestions · recommended 1×
  • CATEGORY QUERY
    Looking for a code review tool with GitHub-style diffs and AI integration.
    you: not recommended
    AI recommended (in order):
    1. GitHub Code Review
    2. GitHub Copilot
    3. CodeQL
    4. GitLab Code Review
    5. GitLab Duo Code Suggestions
    6. Crucible
    7. Review Board
    8. Upsource

    AI recommended 8 alternatives but never named nilbuild/diffity. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How to review GitHub pull requests locally with an interactive diff viewer?
    you: not recommended
    AI recommended (in order):
    1. GitHub CLI (cli/cli)
    2. VS Code (microsoft/vscode)
    3. Beyond Compare
    4. DiffMerge
    5. KDiff3 (KDE/kdiff3)
    6. GitHub Pull Requests and Issues extension (github/vscode-pull-request-github)
    7. IntelliJ IDEA
    8. GitKraken
    9. Sublime Merge

    AI recommended 9 alternatives but never named nilbuild/diffity. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    warn

    Suggestion:

  • 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 nilbuild/diffity?
    pass
    AI did not name nilbuild/diffity — 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?

  • If a team adopts nilbuild/diffity in production, what risks or prerequisites should they evaluate first?
    pass
    AI named nilbuild/diffity 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 nilbuild/diffity solve, and who is the primary audience?
    pass
    AI named nilbuild/diffity 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 nilbuild/diffity. 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/nilbuild/diffity.svg)](https://repogeo.com/en/r/nilbuild/diffity)
HTML
<a href="https://repogeo.com/en/r/nilbuild/diffity"><img src="https://repogeo.com/badge/nilbuild/diffity.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

nilbuild/diffity — 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