在 rove 仓库内跑 auto-motion——把 transcription.srt 拆成多段 MG 动画镜头并拼接成竖屏视频(storyboard 分镜 + theme.md 全片主题 + 逐镜头 claude -p 子进程 + ffmpeg 拼接)。
本 skill 是薄 wrapper:解析 auto-motion 模板根,继承 rove 品牌 theme,执行逻辑以 auto-motion 仓库的 canonical SKILL.md 为准。当用户说"跑 auto-motion"、"把这个字幕稿/口播稿做成视频"、"给 rove 做一条 MG 宣传片"时使用。
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
rove 自己的宣传片优先用
brand-videoskill(单一 Remotion 工程、theme 靠 import、支持真机 replay 镜头)。本 wrapper 只在需要 auto-motion 通用外部工作流(hyperframes 逐镜头子进程)时用。
canonical 执行逻辑在 auto-motion 仓库的 .claude/skills/auto-motion/SKILL.md——本文件不复制那份流程(避免漂移),只做两件事:定位模板根、注入 rove 的上层 theme。
按顺序取第一个命中的:
../auto-motion(workspace sibling,/Users/jacksonc/i/auto-motion)——本地开发副本,可能领先 fork。refs/auto-motion —— 已存在则用。git clone --depth 1 https://github.com/Sma1lboy/auto-motion.git refs/auto-motion(我们的 fork,带 theme/引擎改动;refs/ 已 gitignore,40M 模板不进 rove 仓库)。然后通读 <AUTO_MOTION_ROOT>/.claude/skills/auto-motion/SKILL.md 并按它执行(storyboard → theme.md → 镜头目录 → 顺序执行监控 → 拼接交付)。单镜头模板是 <AUTO_MOTION_ROOT>/exampleFolder/run-claude-ai.sh;scene skills 本仓库 .claude/skills/ 已 vendor 全套(hyperframes*、general-video、image-gen、motion-graphics),直接从这里复制,不必依赖模板根。
在 rove 仓库里跑时,派生 theme.md 前先感知这些品牌源,继承而不是重新发明:
packages/branding(Remotion 品牌管线,landing 片的既有视觉语言)。docs/assets/brand/logos/。claude(DEFAULT_THEME,品牌身份,见 CLAUDE.md)——终端质感、暗底、Claude 橙系强调是默认调性。不要把 scenes/、final.mp4 写进 rove 源码树。在 scratchpad 或用户指定目录建运行工作区,只把 transcription.srt、storyboard、theme 和产物放那里;需要留档的成片再按用户指示移动。
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
中文简介正在准备中。当前显示原文说明。
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
中文简介正在准备中。当前显示原文说明。
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
中文简介正在准备中。当前显示原文说明。
Draft Rove release notes as Changesets. Writes user-facing entries as `.changeset/*.md` files for `@sma1lboy/rove` (consumed into `packages/rove/CHANGELOG.md` at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap rule so GitHub release pages render flowing text.
中文简介正在准备中。当前显示原文说明。
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
中文简介正在准备中。当前显示原文说明。
Turn a rough idea, a bug, or a batch of unsolved problems into well-structured GitHub issue(s) and file them with `gh`, auto-classifying type + labels from the content (recommend, then confirm) and following Rove's conventions (beginner-friendly framing, concrete file pointers, an acceptance checklist, zero AI/Anthropic attribution). Handles single, batch, and "file the unsolved problems" modes. Use when the user says "file an issue", "open a GitHub issue", "draft a good first issue", "batch these as issues", "上报 issue", "提个 issue", "报个 bug", "把没解决的发上去", or wants to hand low-priority tasks to outside contributors. Distinct from the daemon-owned internal issue store (`rove api issue-*`); this skill is for outward-facing GitHub issues.
中文简介正在准备中。当前显示原文说明。