Product specs and PRDs
PMs and engineers can review generated requirements as readable prose and keep decisions attached to the paragraph that needs work.
GitHub-native document review
Review AI-generated specs and docs in GitHub like a document, not a diff.
Commentary opens GitHub pull requests and branches in a reading-first workspace so PMs, engineers, and stakeholders can review rendered Markdown and comment on paragraphs instead of raw diff lines.
Best for specs, ADRs, rollout plans, READMEs, and docs drafted with AI.
- Document-style review
- Paragraph comments
- GitHub pull requests
- Branch review before a PR
Open a GitHub review
Paste a GitHub PR, branch, repo, file, or folder URL to open the matching review surface. Azure DevOps URLs are still supported.
Try a sample review
Explore a realistic GitHub PR review with rendered Markdown and paragraph comments.
AI can draft the doc. Commentary helps your team review it.
AI tools make it faster to draft specs, ADRs, rollout plans, and docs in Markdown. Review still gets stuck in raw diffs, where prose reads like code and stakeholders lose the thread.
Commentary centers the rendered document so reviewers can read the spec the way it will land.
Comments attach to paragraphs and semantic blocks, so feedback stays connected to the idea under review.
GitHub remains the source of truth for pull requests, branches, files, and folders.
Built for real Markdown review jobs
Use Commentary when the important work is understanding prose, not scanning changed lines.
ADRs and technical design docs
Tech leads and staff engineers can discuss tradeoffs in the rendered document instead of translating Markdown diffs back into intent.
Rollout plans and launch docs
Founders, PMs, and operators can check sequencing, risks, and ownership without digging through raw changed lines.
README and docs updates
Docs-as-code teams can review what readers will actually see while keeping the source of truth in GitHub.
Branch review before a PR
Teams can open a branch, folder, or file for document review before the work is ready for a pull request.
How it works
- Paste a GitHub PR, branch, repo, file, or folder URL
- Commentary resolves the right document context
- Review rendered Markdown with paragraph-level comments