1 item
Markdup — A better way to review Markdown files. Markdup shows GitHub Markdown pull request diffs as formatted documents, not as a wall of source. GitHub’s Files changed view treats .md as code. Headings, lists, tables, and diagrams turn into #, -, and pipe characters. A small edit can look like a large rewrite. Markdup loads the file at the pull request base and head, aligns matching sections, and shows each side as rendered Markdown — the way a reader will see it. What you get Rendered Before / After (or Before or After alone) for changed .md and .markdown files Top-level sections stay aligned, so moves and edits stay clear Unchanged sections start collapsed; expand them when you need context Select text in the rendered view and leave a GitHub review comment Fenced Mermaid diagrams render in a sandboxed frame with pan and zoom How to use it Install Markdup and pin it to the Chrome toolbar. Open Settings from the toolbar icon and connect GitHub (OAuth) or paste a personal access token. Open a pull request Files changed page on github.com. On a changed Markdown file, turn on the Markdup switch in the file header. Markdup runs on github.com pull request Files / Changes pages only. It does not run on GitHub Enterprise hosts. Privacy Markdup has no server. Your GitHub token stays in this extension’s private Chrome storage on this browser. Web pages cannot read it. The extension needs access to github.com and api.github.com so it can load file contents and post review comments. It also uses storage to keep your settings. Open source (MIT): https://github.com/hedger-briskteaching/markdup Issues: https://github.com/hedger-briskteaching/markdup/issues
Aug 23, 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.