Sharing a review
Get a review document in front of reviewers. Publish it to Drop, where reviewers comment on the exact spot and your agent answers with the next version, or render it to a page of your own.
Drop renders comark-annotate Markdown, so the document your agent wrote is the page reviewers open. They click a spot on a screenshot or select a sentence to comment, and the agent reads the open comments and publishes the next version. Earlier versions stay in its history.
Add Drop's MCP server to your agent, and sign in with GitHub when it asks:
claude mcp add --transport http --scope user drop https://drop.vitehub.dev/mcp- Ask for the evidence, for example "Capture the pigeon counter's before and after and drop it for review." The
pr-evidenceskill, which comes with the server, captures both states, measures each mark from the page, and answers with a link and a snippet for the pull request. - Paste the snippet into the pull request. Drop keeps pull request evidence until someone deletes it, so the link keeps working after the merge.
Render the document with the plugins it uses, as Renderers shows, and deploy the page with your preview. For a document of screenshots, comark-annotate render writes the page for you; keep the images next to it:
npx comark-annotate render review.md -o review.htmlLink the page from the pull request, or upload it as a CI artifact. GitHub shows HTML files as source, so for evidence that sits in the pull request itself, attach a screenshot of the rendered page.
Which to use
Drop fits a review that goes back and forth: comments sit on the screenshot they're about, and the agent fixes what they ask without anyone copying feedback into a chat. Your own page fits a team that wants no service in the loop, or already reviews on preview deployments.
Either way, write the document first, as A review document shows, and check it with lint-comark before it goes out.
About Drop
Drop is made by the author of these plugins. Anyone with a GitHub account can sign in at drop.vitehub.dev, and a new drop is visible only to you until you share it with your team or by link. Its docs cover sharing, versions, and how long each kind of drop is kept.
Drop is open source under Apache-2.0, so a team can run its own on Cloudflare, Vercel, Netlify, Deno Deploy, or a VPS, and keep its review documents on its own infrastructure.