Esc

A review document

Put a pull request's evidence in one Markdown file. The reviewer reads the decision first, then sees it, then reads the code.

Playground

Decision

Moon phase and vibes collapse into +2 filters, so the toolbar stays on one row at 640px.

Before
Filter toolbar wrapping onto a second row1
  1. 1
    Moon phase and vibes don't fit, so the toolbar wraps and pushes the table down.
After
Filter toolbar on one row2
  1. 2
    Moon phase and vibes collapse into +2 filters.
1 / 2
The changesrc/toolbar.ts+2 −1
const visible = filters;
const visible = filters.slice(0, 3);
const hidden = filters.length - visible.length;
Width Before After
640px 105px 56px
1024px 56px 56px
Try it on the preview deployment pr42.preview.example.com

The order

A reviewer decides whether to approve, so give them the decision first and the evidence after it:

  1. A callout states what changed and why, in a sentence or two. IMPORTANT fits a decision, WARNING a risk the reviewer should weigh.
  2. A ::compare shows the change. Mark the problem in red on the before side and the fix on the after side, so the two sets of notes read as one story.
  3. A ::diff shows the lines that matter. Keep it to a few lines around the change; the pull request already has the full diff.
  4. A table of numbers goes in ::zoom, so a wide one opens at full size.
  5. A link card points to where the reviewer can try it.

Setup

Register the plugins in one renderer, as Renderers shows. This document needs annotate, diff, github, embed, and zoom. Annotate brings zoom with it for the screenshots, and zoom() adds it for the table.

Check it

Run comark-linter on the file before you post it, and open the rendered page to see that each mark sits on its target. Agents shows both commands.

Share it

Sharing a review puts the document in front of reviewers: on Drop, where they comment on the exact spot, or on a page you host.