Markdown PR — Markdown PR Comments for GitHub

🆕 What's new in recent releases v1.12.0 (2026-09-25) • Every rendered comment now offers Copy Markdown, making its original Markdown body easy to reuse in another discussion or document. v1.11.0 (2026-09-23) • Commented table rows and fenced-code lines now keep persistent markers that show conversation counts and cycle through threads. • Every rendered comment now offers Copy link, and bulk rendering is offered only while another Markdown file still needs it. v1.10.0 (2026-09-23) • Authentication is now browser-session only; the dormant Personal Access Token fallback and any legacy saved token are removed without reading or transmitting the token. • Comment actions, Table of Contents navigation, sidebar resizing, Pull requests list navigation, and large-PR guidance are now more direct and reliable. 📌 Just installed? Hard-refresh (Ctrl+Shift+R / Cmd+Shift+R) any GitHub PR tab that was already open when you clicked Add to Chrome — the extension only activates on tabs loaded AFTER install. New tabs work automatically. — GitHub's "Files changed" rich-diff renders Markdown beautifully — design docs, dev plans, READMEs — but provides no way to click on a paragraph and leave a review comment. You have to flip back to source-diff mode to comment, then back again to see how it renders. This extension closes that gap. What it does: • Hover any paragraph, heading, list item, table row, or code block in rich-diff and a blue "+" appears. Click it, type a comment, click Comment. The comment posts as a real PR review comment on the correct source line. • Drag the "+" from one block to another to leave a multi-line range comment. • Existing review threads render inline as "N comments" badges, anchored to the rendered block they belong to. Expand a thread to read, reply, resolve, or unresolve — all without leaving rich-diff. • Commented table rows and fenced-code lines keep persistent markers beside the affected content. Shared rows or lines show a count and cycle through their conversations by mouse or keyboard. • Copy a direct link or the original Markdown body from any visible review comment's header. • Comment box matches GitHub's UI: Markdown toolbar, Write / Preview tabs, @mention autocomplete, Cmd/Ctrl+Enter to submit. • Threads sidebar — a draggable, resizable panel lists every review thread on the page, with prev / next navigation, an "unresolved only" filter, and j / k / h / l keyboard shortcuts. Press `t` to toggle the sidebar, `Shift+T` to reset its position. • Changes tab — a list of every changed block in document order with an added / removed / mixed glyph and a snippet, so you can scan the edits without reading the kept prose. Step through with `[` / `]`, click the page icon in the header to jump to the next change in one tap, or press `1` / `2` / `3` to switch sidebar tabs (Changes / Threads / Outline) from the keyboard. • Outline button in the sidebar header — click the book icon (or press `b`) to switch to the Outline tab. If any Markdown files in a standard PR aren't rendered yet, they're rendered first so the outline has headings to show. On GitHub's optimized large-PR view, the sidebar instead explains that Markdown files must be reviewed and switched to rich diff one at a time because offscreen files are unloaded. • Outline tab — a heading tree of every modified Markdown file with a comment-count pill per section; click to jump, fold individual sections or bulk-fold by level (Fold H1 / H2 / H3 / Expand all). • Heading anchor links (Table of Contents) work in rich-diff — clicking `[Section](#section)` scrolls to the heading. • Avatars and GitHub-native role badges (Author, Owner, Member, Contributor, First-time contributor, …) on every comment. • Collapse sections by heading to focus on what's left to review. No Personal Access Token required — uses your existing GitHub session cookies. Works on public and private repos. No third-party servers, no telemetry, no analytics. Best for PRs that include Markdown content — design docs, dev plans, READMEs, and ADRs. The extension activates wherever GitHub's rich-diff view is available; on source-only files (.js, .py, etc.) GitHub's normal source-diff continues to work as it always has. Open source on GitHub: https://github.com/chienyuanchang/rich-diff-comments — source, issue tracker, and roadmap. — This is an independent, third-party browser extension. It is not affiliated with, endorsed by, sponsored by, or otherwise connected to GitHub, Inc. "GitHub" is a registered trademark of GitHub, Inc., and is used here only to identify the service this extension works with.