Record your screen over the PR, explain the tricky parts out loud, and drop the link into the review. Moonshot adds captions and a transcript, so reviewers can skim the intent before they watch.
Three steps, all async. You narrate the diff once, and every reviewer gets the context on their own time.
Walk the diff in your editor. Explain the approach, the tradeoff, and the exact part you want eyes on.
Skim the transcript in a minute or watch the walkthrough at 2x. Both beat reverse-engineering intent from a diff.
The walkthrough stays in your library. The next person to touch that module watches it before they change it.
Most review comments ask the same question: what were you thinking? Answer it once, out loud, and let it travel with the code.
Architecture calls, the approach you rejected, the hack you plan to remove. Say it in two minutes instead of typing an essay into the PR description.
why > whatThe transcript is searchable text. Reviewers find the line about the migration and jump straight to that moment in the video.
ctrl-F the videoOver MCP, Claude or Cursor reads walkthrough transcripts as context. Your agent learns the codebase the way a teammate would.
Big diffs, subtle refactors, and anything a new teammate will touch next. Two minutes of narration saves three rounds of "why did you do it this way" in the comments.
In your Moonshot library, linked from the PR. Push it to Slack or attach it to the Linear issue in one click, and it stays searchable after the branch merges.
Yes. Moonshot runs an MCP server, so agents can search recordings and read transcripts. Point Cursor at the walkthrough for a module before you ask it to refactor that module.
No. The walkthrough opens from a private link right in the PR or Slack. Only the person recording needs Moonshot, and there is no account required to start.
Free to start, and no account needed until you want to share. Two minutes of narration now saves your reviewers an afternoon of guessing.