Platform Guide — GitHub

AI Chrome extension for GitHub: explain code, READMEs, issues, and PR diffs on screen.

Use Vezz me on github.com to decode unfamiliar source files, understand 80-comment issue threads, and review pull request diffs without leaving your repository tab.

Best fit

Best for developers who browse open-source repositories, review PRs, and triage issues on GitHub in Chrome or Firefox.

On-screen walkthrough

How this looks on a real webpage.

Instead of switching tabs and rebuilding context, highlight the exact passage that slowed you down and press your shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on macOS, fully customizable in settings).

github.com/org/edge-router/pull/182/files
Context: Detailed
1. Highlighted on page (GitHub Pull Request Diff — Worker Cache Middleware)
+ headers.set('Cache-Control', 'public, max-age=3600, s-maxage=86400') + headers.set('Vary', 'Accept, Authorization')
Ctrl+Shift+X“Is setting `public` alongside `Vary: Authorization` safe on shared CDN caches?”
2. Vezz me on-screen answer overlay

**Watch out:** Under HTTP caching specs (RFC 9111), a response to a request containing an `Authorization` header must NOT be stored by a shared CDN cache unless explicit shared-cache directives (`public` / `s-maxage`) are present—which you just added! However, varying on `Authorization` across thousands of unique bearer tokens destroys CDN cache hit ratios and can risk edge misconfiguration leaks if a proxy strips `Vary`. If the response is user-specific, use `Cache-Control: private, no-store` instead.

3. Suggested follow-up questions in thread
  • “What should the header be if we only want to vary on `Accept: text/markdown` for public pages?”
  • “Write a concise PR review comment explaining this risk to the author.”
Step-by-step workflow

How to run this workflow in place.

1

Highlight code lines, PR diffs, or issue comments

Select any code block in a file view, diff hunk in `/files`, or maintainer comment in an issue thread.

2

Press your shortcut (no clash with GitHub hotkeys)

GitHub uses single-key shortcuts (`t`, `s`, `l`, `b`), so Vezz me's default `Ctrl+Shift+X` / `Cmd+Shift+X` chord (or your own custom shortcut configured in settings) triggers cleanly every time.

3

Copy review notes straight into your PR comment

Use one-click copy to paste edge-case questions or explanations into your GitHub review.

Key details

Why this approach works better than switching tabs.

How Vezz me reads GitHub's page context
When you highlight a 10-line function inside a GitHub file view, Vezz me's `Detailed` context mode automatically captures the repository name, file path in the title/URL, and markdown headings.
  • Infers the programming language and framework from the repository title and file extension
  • Keeps the diff view completely visible—no sidebar squeezing side-by-side split diffs
  • Switch to `Minimal` context mode when reviewing sensitive private repositories
Top 3 workflows on github.com
Where developers save the most time on GitHub.
  • 1. Unfamiliar Repo Onboarding: Highlight complex functions or build scripts in a new codebase
  • 2. Issue Triage: Summarize the actual root cause and working fix from long issue threads
  • 3. Security Advisories (GHSA): Decode CVE reproduction steps and patch diffs in place
Frequently asked questions

Common questions about platform guide — github.

Does Vezz me require connecting my GitHub account via OAuth?

No. Vezz me never asks for GitHub OAuth access or repo tokens. It works purely on the text you highlight inside your browser tab.

Does it break GitHub's split diff layout?

No. Unlike sidebar extensions that steal 400px of horizontal width and crush split diffs, Vezz me opens a compact floating overlay that you can drag anywhere or dismiss with one click.

Related workflows & guides

Explore connected pages.

Available for Chrome and Firefox

Ready to try this workflow on your own reading?

Install Vezz me free, highlight text on any webpage, and press your customizable shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on Mac) to get an answer right beside the source.