RRepoGEO

REPOGEO REPORT · LITE

max-sixty/worktrunk

Default branch main · commit 1ad14b29 · scanned 5/16/2026, 4:02:06 AM

GitHub: 5,089 stars · 179 forks

AI VISIBILITY SCORE
40 /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
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 max-sixty/worktrunk, 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
    Clarify the README's H1 and initial positioning

    Why:

    CURRENT
    <h1>&nbsp;&nbsp;Worktrunk</h1> followed by a "May 2026" note and then the core description.
    COPY-PASTE FIX
    Change the H1 to `<h1>&nbsp;&nbsp;Worktrunk: Git Worktree CLI for Parallel AI Agent Workflows</h1>`. Ensure the core description 'Worktrunk is a CLI for git worktree management, designed for running AI agents in parallel.' appears immediately after the H1, removing any introductory text (like the 'May 2026' note) that precedes it.
  • highreadme#2
    Clarify the project's license in the README

    Why:

    COPY-PASTE FIX
    Add a clear 'License' section to the README, stating: 'Worktrunk is licensed under [License Name(s)]. See the LICENSE file for full details.'
  • mediumtopics#3
    Add more specific topics to improve categorization

    Why:

    CURRENT
    agents, claude-code, codex, developer-tools, git, worktrees
    COPY-PASTE FIX
    agents, claude-code, codex, developer-tools, git, worktrees, cli, git-cli, worktree-manager, parallel-development

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 max-sixty/worktrunk
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
ohmyzsh/ohmyzsh
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. ohmyzsh/ohmyzsh · recommended 2×
  2. Git's Built-in Worktree Commands · recommended 1×
  3. VS Code · recommended 1×
  4. eamodio/vscode-gitlens · recommended 1×
  5. jesseduffield/lazygit · recommended 1×
  • CATEGORY QUERY
    How can I efficiently manage multiple Git worktrees for parallel AI agent development?
    you: not recommended
    AI recommended (in order):
    1. Git's Built-in Worktree Commands
    2. VS Code
    3. GitLens (eamodio/vscode-gitlens)
    4. Oh My Zsh (ohmyzsh/ohmyzsh)
    5. LazyGit (jesseduffield/lazygit)
    6. GitKraken
    7. SourceTree

    AI recommended 7 alternatives but never named max-sixty/worktrunk. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are the best CLI tools for simplifying Git worktree creation and switching?
    you: not recommended
    AI recommended (in order):
    1. git-worktree
    2. git-wt (git-wt/git-wt)
    3. git-branchless (arxanas/git-branchless)
    4. fzf (junegunn/fzf)
    5. Oh My Zsh (ohmyzsh/ohmyzsh)

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

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

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

Subscribe to Pro for deep diagnoses

max-sixty/worktrunk — 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