Why start with an unreadable diff?

It establishes the real complexity before offering the summary. The guide calls for about three seconds of sharp, constant-speed scrolling, not blur. If the audience can comfortably read it, adjust the scroll speed rather than removing the short setup that earns the summary.

Does the diff have to be real?

Yes. The premise is the actual shipped change, so invented paths or additions would undermine it. Supply a real change and review its content for secrets and private or unapproved identifiers before using it as visible material.

Can it appear inside my usual coding agent?

The package’s workflow uses an owned or explicitly permitted surface; otherwise it calls for a neutral original terminal with original chrome and icons. State when the interface is representative. Show real repository names and other identifiers only when they are approved for publication.

Is a finished project supplied in the download?

No. The archive contains the production guide, film blueprint, visual system and retarget checklist. An agent uses them to author the ten scenes and render the branded MP4 with the HyperFrames toolchain.

What should the four tiles prove?

Each should show a distinct effect of the actual change with one small piece of evidence, such as a diff fragment, a short flow or a result. If a headline needs two clauses or a capability has no support in the change, simplify or replace it before animating.

Code-Change Explainer Film

Previews from the publisher

Explain the significance of a substantial code change to people who will not read its diff. Code-Change starts with the actual change moving too quickly to follow, then gives viewers the concise summary, invocation and four concrete effects they need instead. A typed install command closes the approximately thirty-second release film.

What you get

A production blueprint for an approximately thirty-second, 1920×1080, 30 fps H.264/AAC MP4. Warm paper, a dark terminal inset and one accent frame a ten-scene sequence rather than a long technical walkthrough.
Instructions for authoring an editable HyperFrames project with scene files, a storyboard covering seven copy-slot types, a cut ledger and a shared palette/type stylesheet. The package contains the guide and reference documents; the project and rendered video are outputs to create.
A detailed opening-scroll specification using actual paths, added/removed lines and counts at roughly 900–1200 pixels per second, without blur. The cut lands while scrolling continues, followed by a short punch line and a readable summary.
A four-tile capability sequence, each carrying one supported effect and a small piece of evidence, followed by the working install command. Music, typing and click/scroll effects support the cut; the blueprint does not use voiceover.

Before you choose

Choose this after the change has a clear stakeholder-level meaning. Write the one-sentence summary first and check that the four tiles support it without repetition. The real diff earns credibility, but the summary and verified closing command are what make the film useful.

Good fit

A substantial shipped change whose value is not reaching stakeholders through an ordinary changelog entry.
A release with a real pull request, commit range or diff export available for the opening material.
A team able to explain the change in one sentence and identify four concrete effects worth separate cards.

Not for

A tutorial or step-by-step engineering walkthrough. The structure is a short release argument, not detailed instruction.
A tiny fix that does not justify a thirty-second film or four meaningful effects.
An engineering audience whose fastest route to understanding is reading the diff directly.

How to use

You say

/hyperframes-code-change-launch We just merged the batch-export rewrite. Nobody reads our changelog — make the 30-second version.

Provide the actual change, one plain-language summary, four supported effects and the closing install or invocation command. Review what may appear publicly, removing secrets, private hostnames, customer information and unapproved identifiers from the material before it enters the film.
Choose the caller’s own interface or a neutral original terminal as the guide specifies. Gather the mark and warm ground/ink/accent/terminal tokens. Do not use a familiar third-party agent shell as a substitute for the product evidence.
Prepare HyperFrames CLI, Node.js 22 or newer and FFmpeg and locate the referenced motion-stack and pr-to-video workflow. Write the seven copy slots and ten-scene timing plan before authoring the project; keep each capability tile to one idea.
Build and test the scroll beat on its own using the real diff at constant speed. It should reveal recognizable diff structure without inviting line-by-line reading. Keep it sharp, cut mid-scroll and give the following summary enough hold time to read.
Build the remaining scenes and soundtrack, check frame snapshots and replay at speed. Verify the closing command against the intended product/version, repeat layout and cut checks after changes, render and inspect the MP4’s dimensions, frame rate, duration and audio. Retain the editable project and material notes with the release.

Requirements and costs

You bring: The real change: a pull request, commit range, branch, or diff export · A one-sentence summary in plain standup language · Four capabilities the change delivers, one per tile · The install or invocation command the film closes on · An interface you own, or approval to build a neutral original terminal
Dependencies: HyperFrames CLI — required · Node.js 22 or newer — required · FFmpeg — required
Outside costs: Not collected yet
Tools used: HyperFrames
Publisher testing: v1.0.0 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT