RRepoGEO

REPOGEO REPORT · LITE

Ataraxy-Labs/weave

Default branch main · commit f99aa951 · scanned 6/22/2026, 1:06:59 AM

GitHub: 1,186 stars · 33 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

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 Ataraxy-Labs/weave, 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 the core value proposition to the very top of the README

    Why:

    CURRENT
    > **Part of the Ataraxy Labs stack** — agent-native infrastructure for software development. See also: sem (semantic version control) · inspect (semantic code review) · opensessions (tmux sidebar for coding agents).
    >
    > Read the manifesto: https://ataraxy-labs.com/#thesis · Essays: https://ataraxy-labs.com/blogs · LLMs: https://ataraxy-labs.com/llms.txt
    
    <p align="center">
      
    </p>
    
    <p align="center">
      <strong>Entity-level semantic merge driver for Git.</strong><br>
      Resolves merge conflicts that Git can't by understanding code structure via tree-sitter.
    </p>
    COPY-PASTE FIX
    Weave is an entity-level semantic merge driver for Git that resolves false conflicts by understanding code structure via tree-sitter, drastically reducing merge conflicts for independent changes.
    
    > **Part of the Ataraxy Labs stack** — agent-native infrastructure for software development. See also: sem (semantic version control) · inspect (semantic code review) · opensessions (tmux sidebar for coding agents).
    >
    > Read the manifesto: https://ataraxy-labs.com/#thesis · Essays: https://ataraxy-labs.com/blogs · LLMs: https://ataraxy-labs.com/llms.txt
  • mediumabout#2
    Refine the 'About' description for clarity and keyword reinforcement

    Why:

    CURRENT
    Entity-level git merge driver. Resolves false conflicts git invents when independent agents edit the same file. ~95% reduction vs. line-based merge.
    COPY-PASTE FIX
    Weave is an entity-level semantic git merge driver that resolves false conflicts by understanding code structure, reducing merge conflicts by ~95% compared to line-based merge.
  • mediumtopics#3
    Add more specific topics related to semantic code merging

    Why:

    CURRENT
    ai-agents, code-intelligence, coding-agents, conflict-resolution, developer-tools, git-merge, llm-tools, mcp, merge-driver, tree-sitter
    COPY-PASTE FIX
    ai-agents, code-intelligence, coding-agents, conflict-resolution, developer-tools, git-merge, llm-tools, mcp, merge-driver, tree-sitter, semantic-merge, code-merge, git-conflict-resolution

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 Ataraxy-Labs/weave
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GitHub Pull Requests
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. GitHub Pull Requests · recommended 1×
  2. GitLab Merge Requests · recommended 1×
  3. Bitbucket Pull Requests · recommended 1×
  4. Beyond Compare · recommended 1×
  5. KDiff3 · recommended 1×
  • CATEGORY QUERY
    How to reduce git merge conflicts caused by independent changes in the same file?
    you: not recommended
    AI recommended (in order):
    1. GitHub Pull Requests
    2. GitLab Merge Requests
    3. Bitbucket Pull Requests
    4. Beyond Compare
    5. KDiff3
    6. VS Code
    7. Prettier
    8. ESLint
    9. Black

    AI recommended 9 alternatives but never named Ataraxy-Labs/weave. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are semantic git merge drivers that resolve conflicts by understanding code structure?
    you: not recommended
    AI recommended (in order):
    1. jq
    2. yq
    3. json-merge-driver
    4. xmldiff
    5. XML Merge
    6. GumTree
    7. SemanticMerge

    AI recommended 7 alternatives but never named Ataraxy-Labs/weave. 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 Ataraxy-Labs/weave?
    pass
    AI did not name Ataraxy-Labs/weave — 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 Ataraxy-Labs/weave in production, what risks or prerequisites should they evaluate first?
    pass
    AI named Ataraxy-Labs/weave 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 Ataraxy-Labs/weave solve, and who is the primary audience?
    pass
    AI named Ataraxy-Labs/weave 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 Ataraxy-Labs/weave. 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/Ataraxy-Labs/weave.svg)](https://repogeo.com/en/r/Ataraxy-Labs/weave)
HTML
<a href="https://repogeo.com/en/r/Ataraxy-Labs/weave"><img src="https://repogeo.com/badge/Ataraxy-Labs/weave.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

Ataraxy-Labs/weave — 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