generate-video

name	generate-video
description	Generates and renders an Azure Bicep update video for this repository. Use when the user wants to generate a summary.json file, render a Remotion video, or create a Bicep update video from a YouTube community call URL, a GitHub release URL, or both.
argument-hint	Provide a YouTube community call URL, a GitHub release URL, or both.
user-invocable	true

Generate Video

Create the repository-standard Azure Bicep update summary and trigger the video pipeline.

When to Use

• Generate a new Bicep release video
• Produce or refresh the root summary.json
• Start the normal TTS and Remotion render flow for this repo

Inputs

Accept any of these:

• A YouTube community call URL
• A GitHub release URL
• Both URLs together

If no YouTube URL is available, that is valid. Leave video_url and thumbnail_url empty in summary.json.

Procedure

1. If a YouTube URL is provided, use fetching-youtube-video to extract the title, description, publish date, thumbnail URL, video URL, and Bicep version.
2. If a specific GitHub release URL is provided, fetch that release directly and extract the tag, publish date, release URL, and body from that page.
3. Otherwise, use fetching-bicep-changelog to retrieve the latest Azure Bicep release notes.
4. Combine the available YouTube metadata and GitHub changelog into the repository summary format by following summarizing-bicep-update.
5. Write the final JSON to the workspace root as summary.json.
6. Do not manually invoke the pipeline unless the user asks. Writing summary.json is enough because the repo hook starts the remaining audio and video pipeline automatically.

Output Contract

The required artifact is the workspace-root summary.json used by the render pipeline.

{
	"version": "0.41.2",
	"release_date": "YYYY-MM-DD",
	"video_title": "...",
	"video_url": "https://www.youtube.com/watch?v=...",
	"thumbnail_url": "https://...",
	"github_url": "https://github.com/Azure/bicep/releases/tag/v0.41.2",
	"headline": "One sentence describing the most important change",
	"highlights": [
		{
			"title": "Feature name",
			"description": "Max 15 words explaining the change",
			"narration": "1-2 conversational sentences adding context or a use case."
		}
	],
	"breaking_changes": ["Short description of breaking change"]
}

Repository Notes

• summary.json must be written at the workspace root, not only under bicep-video/src/
• The hook-owned pipeline handles TTS, scaffold generation, and Remotion rendering after summary.json is updated
• If the release URL and YouTube video point to different versions, stop and ask the user which version should win