HyperFrames PR to Video
Turn a GitHub pull request into a code-change explainer video — diff ingestion, storyboard, frame-by-frame build, final render in HyperFrames
- What
- Turn a GitHub pull request into a code-change explainer video — diff ingestion, storyboard, frame-by-frame build, final render in HyperFrames
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the HyperFrames skill that turns a GitHub pull request into a code-change explainer video: changelog, feature reveal, fix or refactor walkthrough. Acting as orchestrator, the agent ingests the PR deterministically via the `gh` CLI (full file list, diff, contributors, avatars), locks a brief and design system, drafts storyboard and script, generates audio, dispatches frame workers, then renders the final `video.mp4` — with validation gates at each step, including user-gated ones at setup, storyboard and final render. By @heygen-com, listed here with credit to its creator. Honest caveats: heavyweight by design — a multi-step gated workflow, not a one-shot generation; the input must be a code change read via `gh` (no website capture); an optional HeyGen sign-in unlocks hosted voice/BGM, otherwise it falls back to local engines, so relay the sign-in status before proceeding. Companion skills (`/hyperframes`, `/hyperframes-core`, `/media-use`) carry the setup and design rules this skill defers to. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "HyperFrames PR to Video" for me. Turn a GitHub pull request into a code-change explainer video — diff ingestion, storyboard, frame-by-frame build, final render in HyperFrames Repository: https://github.com/heygen-com/hyperframes/blob/main/skills/pr-to-video/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "hyperframes-pr-to-video". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.