← ClaudeAtlas

ozor-changelog-to-videolisted

Convert changelogs, release notes, and version updates into Ozor.ai video prompts. Use this skill whenever the user has a CHANGELOG.md, release notes, GitHub release, version bump summary, or any list of product changes and wants to turn them into a video. Trigger on phrases like 'video from my changelog', 'release notes video', 'make a video from this update', 'announce this release', 'version update video', 'what's new video', 'product update video', 'feature release video', or any request to transform a list of product changes into video format using Ozor.
renalpelvisdeinocheirus70/ozor-skills · ★ 2 · Code & Development · score 75
Install: claude install-skill renalpelvisdeinocheirus70/ozor-skills
# Ozor Changelog-to-Video Converter Transform changelogs, release notes, and version updates into polished, ready-to-paste Ozor.ai video prompts. This skill reads structured change lists and produces scene-by-scene video prompts that announce updates in a visually compelling way. ## Supported Input Types - **CHANGELOG.md** — standard Keep a Changelog format - **GitHub Releases** — release descriptions with tags - **Release notes** — bullet-pointed feature lists - **Version summaries** — "What's New" style documents - **Commit summaries** — grouped commit messages for a release - **Jira/Linear release notes** — exported issue lists ## Workflow ### Phase 1 — Parse the Changelog Read the changelog and extract: 1. **Version number** — the release tag (e.g., v2.4.0) 2. **Release date** — when it shipped 3. **Change categories** — group changes by type: - **New features** — entirely new capabilities - **Improvements** — enhancements to existing features - **Bug fixes** — resolved issues - **Breaking changes** — anything that requires user action - **Deprecations** — features being phased out 4. **Headline change** — the single most impactful or user-requested change 5. **Change count** — total number of changes (used for duration estimation) ### Phase 2 — Prioritize for Video Not every changelog entry deserves a scene. Apply these rules: **Always include:** - The headline feature (biggest or most requested change) - Any new feature that changes the user's w