1 item
Visual inline comments for Markdown documents on GitHub powered by custom git refs backend (refs/md-comments/data). Markdown Comments brings visual, inline collaboration to Markdown documentation directly inside GitHub. Reviewing Markdown files in Pull Requests or repository file views usually requires broad comments or context switching. Markdown Comments closes that gap by allowing anyone to highlight text or select paragraphs on GitHub to start inline discussions, leave nested replies, and add emoji reactions. All discussions auto-save live to dedicated GitHub Issue threads ([md-comments] <filepath>) with zero git commits, zero extra branches, and zero PR clutter. Key Features: 🚀 Zero-Commit GitHub Backend Leave inline feedback and replies in real time. Everything auto-saves instantly under a per-document GitHub Issue. No messy commits or extra branches in your repository. 💬 Inline Text & Paragraph Selection Highlight any text passage or hover over paragraphs in GitHub file diffs and views to open an inline comment composer. 📂 Dedicated PR Workspace Tab Adds a dedicated "Comments" workspace tab to GitHub Pull Requests, making documentation reviews clean and structured alongside code review. 🎯 Fuzzy Text Anchoring Smart paragraph hash and substring matching ensures comment anchors stay accurate even as documents are edited and updated. 👍 Threaded Discussions & Emoji Reactions Engage in rich discussions with nested replies, emoji reactions, and thread resolution status (Open / Resolved). 🔗 Direct File & Line Linking Every comment includes deep clickable links back to exact source files and line ranges on GitHub. 🌐 Cross-Platform Sync Works seamlessly alongside Markdown Comments for VS Code, Cursor, Antigravity, and Obsidian—allowing your entire team to collaborate across their editor of choice. 🔒 Privacy First No external databases or third-party tracking servers. All requests interact directly with official GitHub APIs.
Aug 18, 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.