/pr-to-video Make a 30-second 1920x1080 feature-reveal video from [PR URL]. Lead with what users get, not the diff; show the key code change with the `code-diff` block for one beat only; end on version number + repo URL. No narration, kinetic captions instead. **Spectacle beat:** The added line in the diff ignites — a green light-sweep travels its length and the line blooms as the camera settles on it.
Make it yours. Put your pull request's link where the prompt says "[PR URL]". The rest of the prompt is generic, so keep "Lead with what users get, not the diff" and change the length or the spectacle beat if you want.
Feature-reveal video made from a GitHub PR
A 30-second feature reveal made from a HyperFrames pull request with /pr-to-video. It leads with the benefit ("Your renders just got faster."), shows the change in a code diff with the added lines lit, and ends on the version and repo URL. Captions, no voice.
You'll need
- HyperFrames skills installed (npx skills add heygen-com/hyperframes)
- The code-diff registry block (npx hyperframes add code-diff)
- A motion preamble to paste above the prompt. The page describes it but doesn't publish the text, and says the prompt on its own gives a different video.
- The URL of your own pull request, in place of [PR URL]
How it was made
The page says the video was "rendered from the prompt above, unedited", and the guide's overview calls the gallery "copy-paste prompts, each one-shots a finished video". Every example was run with a shared preamble pasted above the prompt. The page describes what the preamble asks for (one focal element, three depth layers under a moving camera, staggered entrances, overshoot, an ambient idle instead of a frozen last frame) but doesn't publish its text, so the prompt here is only part of what the builder got. The published prompt keeps the placeholder "[PR URL]"; the page doesn't say which PR was used, but the video is labeled "HYPERFRAMES · PR #1928", a change that batches frame capture. The file on the page is a smaller web encode of the render. The agent and model aren't named.
Posted Jul 30, 2026 · HyperFrames prompting guide on Website
Prompt from: Docs page "Verified example prompts", accordion "GitHub PR reveal", under "With registry blocks and workflows"
Look notesby Reference
Dark, warm-toned slides with a faint grid, built from one pull request: a big speed-up figure, a small node-to-Chrome diagram, the code diff, a validation stat, and the version number.
- Color
- Near-black brown with a faint grid and a soft rust glow, off-white type, salmon-orange for the eyebrow labels, the progress rule and the URL box, amber for a "0.0 ms" readout, and a green highlight on the added lines of the diff.
- Type
- Widely spaced monospace caps for the header "HYPERFRAMES · PR #1928", the eyebrows and the footer "FEATURE REVEAL · BATCHED drawElement CAPTURE". A bold sans for "1.20×" and the headlines, a code face for the diff, and a heavy monospace "v0.7.38".
- Framing
- Content set left or centered with wide margins. The header is pinned top-left, and a thin progress rule and the footer run along the bottom of every frame. The diff sits in a dark editor window with its file path underneath and a one-line caption below.
- Sound
- No narration, as the prompt asks; kinetic captions carry the words. The file has an audio track, which the page doesn't describe.
- Structure
- "1.20×" over "MEDIAN · WALL-CLOCK" and "Your renders just got faster.", "THE TAX: every frame pays two round-trips" with frames f1 to f4 passing between node and Chrome, "THE FIX" with f1 to f4 in one box and HF_DE_BATCH=4, an empty editor window, the diff of captureStreamingStage.ts ("the whole change, one branch", "opt in: HF_DE_BATCH=4"), "VALIDATED" with 0 damaged frames and 17/19 bit-identical renders, and "Faster renders. Same pixels." over v0.7.38 and github.com/heygen-com/hyperframes.
