Commentary
Open appTry Commentary
AI document review platform

Review AI-generated docs like documents, not diffs.

Diffs show what changed. Commentary helps teams decide whether it is ready.

Open a review from a URL.

Paste a GitHub PR, branch, repository, file, folder, or Azure DevOps URL.

Open GitHub PRs, branches, repos, files, or folders here. Use the draft action for local Markdown or HTML. Azure DevOps URLs are supported.

Try the demoSee how it works
GitHub PRMarkdownHTMLKnowledge BrainDraft reviewAgent-readyPrivate by default
commentary review workspace
acme / ai-docs
ReviewingPrivate
#184 Review AI-generated launch guide
GitHub PRRendered Markdown5 section commentsAgent-ready
Branch: ai-docs-refreshPrivate workspaceReady for agent
Files
launch-guide.md
support-handoff.md
faq.md
Rendered Markdown

Enterprise rollout plan

Clarify launch sequence, customer impact, and owner for each readiness milestone before merge.

Diffs show what changed. Commentary keeps readiness feedback attached to the section it belongs to.

Comment threads
Docs

This claim needs customer-facing evidence before release.

Agent

I can revise the rollout section with this context.

Context packet preparedPatch scoped to selected section
Why diffs break down

AI-generated docs need review on meaning, not just changed lines.

Raw diffs are useful evidence, but they are a poor primary surface for deciding whether product work, docs, or generated specs are ready.

Raw diff review

  • Raw GitHub diffs hide the document readers will actually see.
  • Line-level comments break when AI rewrites a section.
  • Reviewers debate syntax without enough product or launch context.
  • Agents receive scattered notes that are hard to turn into a focused patch.

Commentary review

  • Rendered documents, specs, and previews stay at the center of review.
  • Section-level comments stay attached to meaning as drafts change.
  • Context-rich threads capture readiness decisions in one workspace.
  • Agent-ready feedback gives authors and coding agents clear next actions.
How Commentary works

A connected loop from first read to final revision.

Open the work, review it as an artifact, and keep every readiness decision attached until an author or agent resolves it.

  1. 01

    Open a review

    Start from a GitHub PR, branch, folder, draft, knowledge base, or opted-in live preview.

  2. 02

    Read the rendered work

    See Markdown, HTML, and preview surfaces in the form teammates need to evaluate.

  3. 03

    Comment on meaning

    Attach feedback to sections, claims, UI states, and product decisions.

  4. 04

    Agent or author resolves

    Hand structured feedback to the person or agent making the next revision.

  5. 05

    Ship with confidence

    Keep review state, source context, and final decisions together through merge.

Review surfaces

Use the same review model wherever the work starts.

Commentary supports the Git-backed, static HTML, knowledge-base, draft, and preview-based surfaces teams already use for AI-generated documentation, specs, and product work.

PR review

GitHub PRs

Turn Markdown-heavy pull requests into rendered review workspaces with durable threads.

Explore surfaceRepo docs

Branches and folders

Open repository Markdown or HTML by branch, file, or folder when the work is not a single PR.

Explore surfaceStatic HTML

HTML pages

Review static HTML pages in sandboxed Preview and Raw modes across PRs, branches, and drafts.

Explore surfacePre-PR review

Drafts

Review plans, specs, release notes, and ADRs before they become branches.

Explore surfaceStructured answers

Forms

Collect structured answers from review-hosted forms, response links, result collections, and git sync.

Explore surfaceSecond brain

Knowledge Brain

Review AI-maintained knowledge bases with brain-aware navigation, health context, and evaluations.

Explore surfacePreview SDK

Live previews

Opt into browser-based review for UI and docs previews that need element-level context.

Explore surface
Built for the AI review loop

AI writes. Humans review. Agents revise. Commentary keeps the conversation attached to the work.

Section-level feedback gives agents more than a line number. It gives them the rendered content, selected block, surrounding context, and decision trail they need to make the next edit.

Agent-ready feedback

A comment becomes a context packet: what was reviewed, why it matters, and what action should happen next.

Comment -> context -> patch
Agent

  1. Reviewer comments on a rendered section.

  2. Commentary packages section context and source metadata.

  3. Agent or author returns with a focused revision.

Reviewer
Use cases

Focused workflows for teams reviewing generated work.

The same document-first model supports docs quality, engineering decisions, agent revision loops, and product review.

Documentation teams

Review docs branches, READMEs, and release notes as reader-facing documents.

Learn more

Engineering teams

Keep ADRs, design docs, rollout plans, and operational guidance clear before merge.

Learn more

AI agents

Give coding agents comments with enough section context to revise the work cleanly.

Learn more

Product & design

Align on product specs, launch narratives, and preview details before they ship.

Learn more
Safe for developer teams

Private by default, provider-aware, and explicit about access.

Commentary keeps source access, review state, telemetry, and preview opt-in boundaries clear so teams can evaluate generated work without changing their security posture.

Read the security overview

Private by default

Public PRs stay readable, while private repositories and write actions require authentication.

  • No surprise public previews
  • Auth required for comments

Provider-aware

Review routes keep GitHub and Azure DevOps boundaries explicit at server and API edges.

  • Git-backed source context
  • Provider-scoped flows

Scoped access

Commentary asks for review-specific access instead of turning provider identity into telemetry.

  • Privacy-safe analytics
  • Advanced PAT recovery

Explicit preview opt-in

Live Preview Reviews load customer-owned previews; the SDK enables selector context and screenshot comments require explicit browser capture.

  • SDK selector context
  • Explicit cropped capture

Ready to review better?

Start with a GitHub PR, branch, HTML page, knowledge base, draft, or live preview.

Try Commentary for freeOpen a review