Draft Reviews

Review drafts before they become branches.

Create a private review from local drafts, AI-generated drafts, Markdown, MDX, HTML, or text before the work is ready for a branch or PR.

Draft Reviews use the same rendered review model as Git-backed pages, but the entry point is pasted or uploaded content.

  • Paste or upload
  • Rendered review
  • Private sharing
  • Revisions

From draft to reviewable document.

The draft flow stays intentionally simple: get content into Commentary, review the rendered artifact, then revise or export when the team is ready.

Draft or paste

Markdown, MDX, HTML, or text enters Commentary.

Rendered review

Reviewers comment on the readable artifact.

Revision

New content keeps the thread history close.

Export or share

Use the latest export, share link, or structured handoff.

Workflow.

Draft Reviews cover the private pre-Git loop without pretending the work has already moved to a provider.

  1. 01

    Create draft

    Paste or upload the files that need review.

  2. 02

    Rendered review

    Invite reviewers into the readable Commentary session.

  3. 03

    Revise

    Upload a new revision while keeping thread history visible.

  4. 04

    Export or share

    Use the latest export, share link, or developer handoff when the draft is ready.

Private review before Git exists.

Draft Reviews are built for the stage where the source is still a local file, generated output, pasted text, or a private session.

Bring generated drafts in.

AI-generated plans, specs, and notes can be pasted or uploaded before they belong in Git.

Keep revisions together.

Revision history lets reviewers compare the latest draft with the previous version without losing the conversation.

Hand feedback back out.

Share links, exports, and structured instructions give people or agents the context they need to revise the source draft.

Explore developer tools
Pre-Git review

A private loop for work that is not ready for a provider.

Use Draft Reviews for generated specs, local docs, HTML previews, and stakeholder copy that needs human comments before it becomes a branch.

Private sessionRendered revisionsExport or agent handoff

Review a draft before it becomes a branch.

Start with the content you already have and move to Git when the decision is clearer.