tldraw/tldraw

Overview

This skill creates a narrated MP4 walkthrough of a GitHub pull request, combining code slides, unified diffs, and audio narration into a single 1600x900 video file. It produces a standardized intro/outro, per-segment audio clips, and a manifest that drives a Remotion renderer so reviewers can quickly understand what changed and why.

How this skill works

Point the skill at a PR URL or number (default: tldraw/tldraw). It reads the PR diff and commits, writes a continuous narration script, generates a single TTS audio file and per-segment clips, then builds a manifest.json describing intro, diff, code, segment, and outro slides. Finally it runs the renderer to produce the final MP4 and stores intermediate artifacts in a temporary, gitignored folder.

When to use it

• You want an author-perspective walkthrough that explains both what changed and why.
• You need a shareable internal artifact to speed PR review onboard new contributors.
• A complex change spans multiple files and benefits from guided, line-focused narration.
• You prefer a consistent, repeatable video format for release notes or team updates.
• You want to attach a visual walkthrough to a PR for asynchronous review.

Best practices

• Write the full narration first, then map each sentence to the code or diff the viewer should see.
• Keep segments focused: intro → context → code walkthroughs → summary, with 8–12 segments total.
• Include only relevant hunks in diff slides and add focus points for content >30 lines.
• Generate one full WAV and split into clips for consistent voice and pacing; avoid ad-hoc pauses in text.
• Store only the final MP4 in out/ and keep audio/manifest in the gitignored tmp/ directory.

Example use cases

• Author records a walkthrough for a large refactor to explain the new architecture and key functions.
• Team lead prepares a review summary for a bugfix that touches many files and edge cases.
• Onboarding: attach a walkthrough video to a PR to accelerate a new contributor’s context.
• Release notes: create a narrated highlight of a feature PR to show designers and PMs.
• Cross-team sync: share a concise explainer of a performance optimization with engineers.