ce-demo-reel

Run the demo reel capture flow, which records the feature in action, stitches frames into an animated GIF via ffmpeg, and uploads it to a public URL. The returned URL can be embedded directly in the PR description as an image.

Terminal recordings use VHS from Charmbracelet to execute a tape file and produce a GIF. Screenshot reels use silicon to render styled frames and ffmpeg with ffprobe to stitch them into an animated GIF.

Set real credentials inside a VHS Hide block or before recording starts so they never appear on screen. The workflow scans artifacts for tokens like sk- or Bearer before upload and requires recapture instead of blurring if anything leaks.

Yes, the detect command classifies the project from package.json, Gemfile, go.mod, Cargo.toml, or pyproject.toml. Web apps use agent-browser screenshots stitched into GIFs, while CLI tools use VHS recordings or silicon-rendered frames.

The stitch command targets 5 MB and enforces a 10 MB ceiling matching GitHub's inline render limit. If the output exceeds the limit, it automatically drops middle frames and re-stitches to reduce size.

Skip evidence when the diff is docs-only, markdown-only, config-only, CI-only, test-only, or a pure internal refactor with no observable output change. The workflow also offers a 'No evidence needed' option during tier selection.