5 items
Understand any GitHub repo without reading every file. Architecture, dependencies, user flows — mapped to actual code. Reading code top-to-bottom doesn't scale. You need a map of the codebase, not a tour through every file. That's what Revibe builds. Click "Analyze with revibe" next to GitHub's Code button. In 2–5 minutes you get: • Architecture diagrams — modules, layers, how the pieces talk • Dependency graph — what calls what, where the seams are • User journey → code — trace a real flow (signup, checkout, an API call) down to the lines that run it • File-by-file roles — what each file is actually responsible for • System design Q&A — the "why is this here" answers in plain English • Database schema, if the repo has one • AI-agent context export — a JSON brief you can hand to Claude, Cursor, or Codex instead of pasting in files Built for engineers who need to understand code they didn't write: • Reviewing what your AI agent shipped • Onboarding to a legacy or unfamiliar repo • Auditing an open-source dependency before adopting it • Learning architecture from real production code How it works: 1. Sign in at revibe.codes (free — 1 project credit, no card needed) 2. Open any GitHub repo 3. Click "Analyze with revibe" next to the Code button 4. Pick your depth — new to the stack, intermediate, or expert 5. Get the briefing Privacy & permissions: • Only the repo URL you choose to analyze is sent to Revibe • Your auth token lives in local browser storage, never shared with third parties • Full policy: https://www.revibe.codes/privacy.html
May 28, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.