RRepoGEO

REPOGEO REPORT · LITE

Opencode-DCP/opencode-dynamic-context-pruning

Default branch master · commit 0657cd2f · scanned 5/14/2026, 9:57:32 AM

GitHub: 2,783 stars · 145 forks

AI VISIBILITY SCORE
22 /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
1 / 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 Opencode-DCP/opencode-dynamic-context-pruning, 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 the repository

    Why:

    COPY-PASTE FIX
    opencode, llm-plugin, context-management, token-optimization, ai-assistant, generative-ai, chat-history
  • highreadme#2
    Update the README's main heading to include 'OpenCode'

    Why:

    CURRENT
    # Dynamic Context Pruning Plugin
    COPY-PASTE FIX
    # OpenCode Dynamic Context Pruning Plugin
  • mediumhomepage#3
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    Add a link to the OpenCode project or a dedicated plugin page for more information.

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 Opencode-DCP/opencode-dynamic-context-pruning
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LangChain
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. LangChain · recommended 2×
  2. LlamaIndex · recommended 2×
  3. Haystack · recommended 2×
  4. gpt-3.5-turbo · recommended 2×
  5. gpt-4 · recommended 2×
  • CATEGORY QUERY
    How to dynamically manage AI conversation context to optimize token usage and reduce costs?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Haystack
    4. OpenAI API
    5. gpt-3.5-turbo
    6. gpt-4
    7. tiktoken
    8. Pinecone
    9. Weaviate
    10. Qdrant
    11. Milvus
    12. Redis

    AI recommended 12 alternatives but never named Opencode-DCP/opencode-dynamic-context-pruning. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a tool that intelligently prunes chat history for large language models to save tokens.
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. ConversationBufferWindowMemory
    3. ConversationSummaryBufferMemory
    4. LlamaIndex
    5. ChatMemory
    6. Haystack
    7. InMemoryChatMessageStore
    8. ConversationSummaryMemory
    9. gpt-3.5-turbo
    10. gpt-4
    11. LiteLLM
    12. Guidance

    AI recommended 12 alternatives but never named Opencode-DCP/opencode-dynamic-context-pruning. 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 Opencode-DCP/opencode-dynamic-context-pruning?
    pass
    AI named Opencode-DCP/opencode-dynamic-context-pruning explicitly

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

  • If a team adopts Opencode-DCP/opencode-dynamic-context-pruning in production, what risks or prerequisites should they evaluate first?
    pass
    AI did not name Opencode-DCP/opencode-dynamic-context-pruning — 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?

  • In one sentence, what problem does the repo Opencode-DCP/opencode-dynamic-context-pruning solve, and who is the primary audience?
    pass
    AI did not name Opencode-DCP/opencode-dynamic-context-pruning — 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 Opencode-DCP/opencode-dynamic-context-pruning. 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/Opencode-DCP/opencode-dynamic-context-pruning.svg)](https://repogeo.com/en/r/Opencode-DCP/opencode-dynamic-context-pruning)
HTML
<a href="https://repogeo.com/en/r/Opencode-DCP/opencode-dynamic-context-pruning"><img src="https://repogeo.com/badge/Opencode-DCP/opencode-dynamic-context-pruning.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

Opencode-DCP/opencode-dynamic-context-pruning — 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