Rendered for reading.
Headings, lists, links, and prose appear as the reviewer will experience them.
Markdown Review
Review Markdown that's clear, current, and ready to decide.
Commentary turns GitHub PRs and branches into clean Markdown previews so your team can review the document before the diff becomes the whole story.
Open public PRs read-only where GitHub allows it, then sign in when you need to comment, refresh, or submit staged review feedback.
- GitHub PRs
- Repository branches
- Rendered preview
- Contextual comments
See the Markdown that matters.
Preview, Raw, Latest, and Diff stay simple. The rendered document is the default, while source and changes remain close when a decision needs them.
Source when syntax matters.
Frontmatter, MDX, and exact Markdown remain one switch away.
The current document.
Read the newest version first, without making the diff the whole page.
Changes in context.
Use changed-block navigation when the decision depends on what moved.
How it works.
A GitHub URL becomes a readable document review without replacing the Git workflow your team already trusts.
- 01
Open a PR or branch
Paste a GitHub PR, branch, file, or folder URL.
- 02
Read the rendered doc
Commentary turns the source into an editorial preview.
- 03
Use tools as support
Preview, Raw, Latest, and Diff are available when the decision needs them.
- 04
Submit through GitHub
Resolve content feedback before staged review comments are submitted.
Comments that connect to meaningful blocks.
Feedback attaches to a section, document block, or selected text under review, so the thread follows the idea instead of becoming a detached line note.
Select the prose.
Reviewers highlight the sentence, paragraph, or section that needs a decision.
Keep context visible.
The thread records the comment beside the rendered Markdown while the source remains available.
Why rendered review
AI-generated docs need reading context before line context.
Raw diffs are still useful, but they should answer targeted questions after reviewers understand the document.
Raw diff review
- AI-generated prose is chopped into line movement instead of reading flow.
- Reviewers debate Markdown syntax before they understand the document.
- Threads drift away from headings, sections, and resolved decisions.
Rendered Markdown review
- The document opens as the reader will experience it.
- Preview, Raw, Latest, and Diff stay available as supporting tools.
- Comments attach to sections, selected text, and semantic blocks.
Built for how your team already works.
Commentary keeps GitHub as the source of truth while giving Markdown the reading surface it needs.
No new repository workflow. Faster content decisions. Better quality before merge. Provider access and private content stay tied to the authenticated GitHub boundary.
Ready to review Markdown the right way?
Start with a GitHub PR or try the sample review flow.
Rollout readiness
Launch can proceed once customer support has the fallback language.
The rollback owner is currently implied, not named.