works great. A much needed UI fix for the github UI.
Markdown PR — Markdown PR Comments for GitHub
- 267 users
- 5.005 ratings
- #4,116in Developer Tools
Comment, reply, resolve, and collapse sections directly in GitHub PR rich-diff (rendered markdown) view.
- Users
- 267
- #4,116 of 31,330 in category
- Rating
- 5.00
- 5 ratings · median 4.63
- Version
- 1.14.0
- 153 KiB · Manifest V3
- Access
- Low3/100
- No permissions + 1 site pattern
Description
As written by the publisher on the store🆕 What's new in recent releases
- v1.14.0 (2026-11-03)
- View options lets you show or hide removed content and resolved comments independently, with a highlighted funnel whenever either is hidden.
- Comments stay on the correct lines on newer GitHub file pages, and deleting a comment no longer returns you to a previously visited section.
- v1.13.0 (2026-10-16)
- Rendering all Markdown files now shows live progress, supports Cancel and Escape, and returns you to the same reading position.
- Threads, Changes, Outline, and rendered Table of Contents links now reach distant targets reliably in one action.
- 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.
📌 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 review threads on the page, with prev / next navigation and j / k / h / l keyboard shortcuts. Press `t` to toggle the sidebar, `Shift+T` to reset its position.
- View options — open the sidebar's funnel menu for independent Show removed content and Show resolved comments checkboxes. Hide deleted prose for easier reading or hide resolved conversations throughout the document and Threads. The funnel stays highlighted whenever either option is hidden.
- 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.
Also use Azure DevOps? Our companion extension offers similar Markdown pull request review capabilities in Azure DevOps Preview: https://chromewebstore.google.com/detail/markdown-pr-comments-for/habbfnkhgmnkhlbakjlnapadamjijbdh
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.
Ratings and reviews
Split of the 3 written reviews we hold3 written reviews we hold
Great extension! This solved the biggest pain of me in reviewing md files generated from LLM or my coworkers in my software development cycle. Thank you for doing this!
Track Markdown PR on Radar
This page shows the listing as it is today. Add it to Radar and get one email when it changes.
- Users and rating
- Store text and screenshots
- Permissions it asks for

Markdown PR, in plain words
What it is, what to use instead, what it can access and how to fix it.
Markdown PR at a glance
Markdown PR — Markdown PR Comments for GitHub is a Developer Tools extension with 267 users. Chrome Web Store users rate it 5.00 out of 5 from 5 ratings, which is still a small sample. By users it sits in the top 25% of Developer Tools extensions.
- By users
- #4,116of 31,330 in Developer Tools
- Rating
- 5.00category median 4.63
- Access
- Low3 of 100
Markdown PR alternatives
Closest by what they do · users as the store shows themIs Markdown PR safe?
Markdown PR asks for 0 permissions and access to 1 site pattern. None of them are on our list of wide-access permissions.
Permissions show what it could do, not what it does. See the full permission list.
Every permission Markdown PR asks for
No permissions + 1 site pattern · none sensitive · Low access overallSites
- Read and change data on matching sites
https://github.com/*
Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.
Markdown PR not working?
What recent reviews say
Store reviews from the last 90 daysCommon fixes
Try them in this order- 1Update Chrome and the extension
- 2Turn it off and on in chrome://extensions
- 3Reload the page
- 4Turn other extensions off in case two clash
Still stuck? Contact the maker or try an alternative.
Know when a listing changes
Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.