---
title: "AI Chrome extension for GitHub: explain code, READMEs, issues, and PR diffs on screen."
description: "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."
canonical_url: "https://vezz.me/for/github/"
type: "pseo-for"
category: "for"
topic: "Platform Guide — GitHub"
intent: "Best for developers who browse open-source repositories, review PRs, and triage issues on GitHub in Chrome or Firefox."
---

# 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.

## Live Webpage Walkthrough

- **Source:** GitHub Pull Request Diff — Worker Cache Middleware (`github.com/org/edge-router/pull/182/files`)
- **Recommended Context Mode:** Detailed

**Highlighted Passage:**
> + headers.set('Cache-Control', 'public, max-age=3600, s-maxage=86400')
+ headers.set('Vary', 'Accept, Authorization')

**User Question (Shortcut):** "Is setting `public` alongside `Vary: Authorization` safe on shared CDN caches?"

**Vezz me On-Screen Answer:**
**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.

**Suggested Follow-Ups:**
- "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

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.

## 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

### 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 guides

- [Summarize GitHub PRs & issues](https://vezz.me/use-cases/summarize-github-pull-requests-and-issues/): Step-by-step workflow for long issue threads and RFCs.
- [Senior Engineer Code Reviewer prompt](https://vezz.me/prompts/senior-engineer-code-reviewer/): Download our JSON prompt preset for code review.
- [Vezz me for Software Developers](https://vezz.me/for/software-developers/): Full role guide for engineering teams.