Skip to main content
Use this workflow when the source is a GitHub pull request or a specific code change. The agent reads the PR, identifies what changed and why it matters, then turns that into a short visual explanation.

From a film built out of a real pull request — the diff, the files, and the review, on screen.

​
Start with the PR

Say who the video is for:
  • users need the outcome and any action they must take;
  • contributors may need architecture and tradeoffs;
  • a social audience needs one clear change and visible proof.

​
Approve the angle

Confirm:
  • the intended PR and target branch;
  • whether the audience cares about user impact, architecture, or both;
  • the release state: proposed, merged, released, or planned;
  • the before-and-after behavior;
  • breaking changes or migration work;
  • the maximum level of code detail.

​
Check the facts

Before export:
  • verify the PR is the intended source;
  • distinguish shipped behavior from planned follow-up;
  • do not turn test coverage or refactoring into a user-facing claim;
  • include breaking changes and migration steps;
  • confirm issue, version, and product names.
Use Studio Storyboard to review the explanation and Source when a code excerpt needs adjustment.

​
Common problems

Review in Studio

Check the facts, sequence, code excerpts, timing, and final release language.

Choose another workflow

Return to the source-and-outcome chooser.