pr-to-video

Generate storyboarded explainer videos from GitHub pull request data.

Updated May 6, 2026
One-click install
npx skills add https://github.com/johan-Rm/agents --skill pr-to-video-johan-rm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-to-video
Source: https://github.com/johan-Rm/agents/tree/main/skills/pr-to-video
Command: npx skills add https://github.com/johan-Rm/agents --skill pr-to-video-johan-rm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, hyperframes, ffmpeg, ffprobe, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill solves the challenge of communicating complex code changes to stakeholders by automatically generating high-quality, frame-by-frame explainer videos directly from GitHub pull requests.

Core Features & Use Cases

  • Automated Ingestion: Fetches PR diffs, commits, and file metadata using the GitHub CLI to understand the context of changes.
  • Narrative Orchestration: Plans and generates a storyboard and script tailored to the specific PR archetype, such as a feature reveal, fix-explainer, or refactor-walkthrough.
  • Visual Design: Applies a consistent, professional design system to visualize code hunks and contributor credits.
  • Use Case: A developer needs to explain a substantial refactor to non-technical stakeholders; this skill generates a 90-second video walkthrough that highlights the key improvements and impact of the PR.

Quick Start

Use the pr-to-video skill to generate an explainer video for the pull request at the provided GitHub URL.

Frequently Asked Questions about pr-to-video

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a GitHub pull request into a code explainer video?

You can create a code explainer video by providing a GitHub pull request URL; the skill ingests PR diffs and metadata via the GitHub CLI, generates a storyboard, and renders the video using HeyGen and ffmpeg.

What is the best way to automate changelog video generation for feature releases?

Automating changelog video generation is best achieved by ingesting GitHub pull request data to automatically plan a narrative and generate frame-by-frame visual walkthroughs tailored to the specific PR archetype.

Do I need the GitHub CLI installed to generate pull request walkthroughs?

Yes, you need the GitHub CLI installed because the skill depends on it to fetch PR diffs, commits, and file metadata required to understand the context of the code changes for the video narrative.

Can I use ffmpeg and hyperframes to visualize code hunks for technical communication?

Yes, the skill uses ffmpeg and hyperframes to apply a consistent design system, rendering professional frame-by-frame visual compositions that highlight code hunks and contributor credits for stakeholders.

What types of pull requests work best for generating automated explainer videos?

Automated explainer videos work well for feature reveals, fix-explainers, and refactor-walkthroughs, generating tailored storyboards and scripts suited to each specific pull request archetype.

When should I not use automated video generation for pull request documentation?

You should avoid automated video generation for trivial changes or minor fixes where a simple text changelog suffices, as the overhead of narrative orchestration and visual rendering provides minimal stakeholder value.