RRepoGEO

REPOGEO REPORT · LITE

ezyang/ghstack

Default branch main · commit d0f34240 · scanned 6/11/2026, 7:11:39 PM

GitHub: 991 stars · 85 forks

AI VISIBILITY SCORE
35 /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
3 / 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 ezyang/ghstack, 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 specific topics to improve categorization

    Why:

    COPY-PASTE FIX
    git, github, cli, stacked-diffs, pull-requests, code-review, developer-tools, workflow
  • highreadme#2
    Strengthen the README's opening sentence to emphasize 'dependent diffs'

    Why:

    CURRENT
    # ghstack

Conveniently submit stacks of diffs to GitHub as separate pull requests.
    COPY-PASTE FIX
    # ghstack

Conveniently submit and manage *stacks of dependent diffs* to GitHub as separate pull requests, streamlining complex code reviews.
  • mediumabout#3
    Refine the repository description to be more explicit about 'dependent' PRs

    Why:

    CURRENT
    Submit stacked diffs to GitHub on the command line
    COPY-PASTE FIX
    A command-line tool to submit and manage stacks of *dependent* diffs as separate GitHub pull requests.

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 ezyang/ghstack
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GitHub Draft Pull Requests
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. GitHub Draft Pull Requests · recommended 1×
  2. withgraphite/graphite · recommended 1×
  3. git-town/git-town · recommended 1×
  4. git-stack/git-stack · recommended 1×
  5. cli/cli · recommended 1×
  • CATEGORY QUERY
    How to manage a series of dependent pull requests on GitHub efficiently?
    you: not recommended
    AI recommended (in order):
    1. GitHub Draft Pull Requests

    AI recommended 1 alternative but never named ezyang/ghstack. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a command-line tool to streamline submitting multiple stacked commits as separate PRs.
    you: not recommended
    AI recommended (in order):
    1. Graphite (withgraphite/graphite)
    2. git-town (git-town/git-town)
    3. git-stack (git-stack/git-stack)
    4. gh (GitHub CLI) (cli/cli)
    5. hub (GitHub's unofficial CLI) (github/hub)

    AI recommended 5 alternatives but never named ezyang/ghstack. 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 ezyang/ghstack?
    pass
    AI named ezyang/ghstack explicitly

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

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

Subscribe to Pro for deep diagnoses

ezyang/ghstack — 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