원클릭으로
commit
Create a git commit with a conventional commit message based on staged or unstaged changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Create a git commit with a conventional commit message based on staged or unstaged changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Autonomously generate a short film end-to-end (self-collected public-domain assets + self-composed score + Remotion motion), then self-critique and evolve along a strict capability ladder with PERSISTENT cross-session memory. Each invocation = ONE evolution cycle (reflect → decide → produce → render → critique → record → maybe level-up). Triggers: "make a video", "auto video", "evolving-video", "next video / 下一支", "evolve the video skill", "自主做视频", "run a video evolution cycle", or any open-ended "make something to impress / attract views". Design adapted from karpathy/autoresearch (modify→run→evaluate→keep/discard→repeat on a fixed budget; program.md→EVOLUTION.md; explicit file ledger instead of git history).
把一个网页版 deck(Vite+React+TS,通常由 web-video-presentation skill 产出,如 audiobooks/<id>/presentation/)用 Remotion 帧级重渲成「颜色不失真」的 4K MP4,并可选垫入很轻的 BGM。解决录屏的两大痛点:①录屏颜色失真 → Remotion 输出 sRGB 保真;②手动录屏节奏不稳 → 帧精确、音画锁定。**核心铁律:Remotion 不渲染 CSS animation/transition(逐帧渲染时页面时钟冻结,内容会在第0帧直接定格到最终态 → 表现为「太快/没渐变」);所有入场动画必须用 useCurrentFrame()+interpolate()/spring() 帧驱动**,本 skill 提供可复用的动画原语库(useReveal/useStamp/useProgress/useDraw)与转换套路。时长 = 每步音频长度 + 120ms trail(与网页版 audio.onended+trailMs 一致,由 gen_timeline.py 从 mp3 实测生成)。触发场景:把有声书/演示 deck 渲成 4K 视频、"Remotion 视频太快/没有渐变/动画不播/颜色对但节奏不对"、给已渲染视频加淡淡的背景音乐压噪底。本项目实样:audiobooks/sanen/remotion/。
把一篇文章或口播稿,做成"看起来像视频"的点击驱动 16:9 网页演示,可选合成口播音频。流程:原始文章 → **一次产出**口播稿 + outline 开发计划 → 用户**一次对齐** 5 件事(稿子 / outline / 主题 / 素材 / 开发模式)→ 网页开发(逐章 / 顺序 / 并行)→ 可选音频合成(provider-agnostic:内置 MiniMax mmx-cli + OpenAI TTS,可换 ElevenLabs / edge-tts / Azure / 自带 TTS)。**outline 只规划节奏与信息密度,不规划动画** —— 动画由章节开发时按 PRINCIPLES + ANTI-AI 法则即时设计。每次点击推进口播稿的一个节拍,每一步独占整屏,进度条平时隐藏只在悬浮时出现。适用场景:用网页做视频(动态 PPT 但不像 PPT)、把口播稿 / 文章变成可交互的解说、为 B 站 / YouTube / 视频号录屏教程、做有电影感的产品 / talk demo。本 Skill 沉淀的是设计方法论 + 协作流程 —— 不绑定任何特定样式 / 字体 / 颜色 —— 因此能复用到任意主题与美学。
Cross-project development intelligence. 20 Flask patterns, 18 Electron patterns, 20 frontend patterns, 15 Windows pitfalls, 12 git/release workflows, 15 code conventions, 12 security patterns, 15 Next.js patterns, 15 Python patterns. BM25 search engine. Actions: scaffold route, build feature, fix bug, configure build, debug pitfall, review code, release version, setup project. Stacks: Flask + vanilla JS, Electron + PyInstaller, Next.js + React + Prisma, FastAPI + SQLite, pure Python CLI. Shared across all projects.
Drive Google Flow (Veo 3.1) through a debug-port Chrome (chrome-devtools MCP) to produce a multi-shot cinematic short film end-to-end — storyboard → shot-by-shot generation → character-consistent casting → review → download → post-production plan — then self-critique and EVOLVE along a capability ladder with PERSISTENT cross-session memory. One invocation = one production cycle (or one continuation of an in-flight film). Triggers: "用 Flow 做视频", "Veo 短片", "flow-cinema", "拍一部短片", "继续拍 / 下一幕", "labs.google flow", "把这个概念拍成3分钟". Design adapted from karpathy/autoresearch (modify→run→evaluate→keep/discard→repeat on a fixed budget; program.md→EVOLUTION.md; explicit file ledger instead of git history). Sibling of evolving-video, but the render engine is Veo-via-browser, not Remotion.
Generate RESTful API endpoint code including controller, service, repository, entity, and DTO layers. Use when the user wants to create a new API, endpoint, or interface.
SOC 직업 분류 기준
| name | commit |
| description | Create a git commit with a conventional commit message based on staged or unstaged changes. |
| disable-model-invocation | true |
| allowed-tools | Bash |
Create a git commit for the current changes.
git status to check current changesgit diff and git diff --staged to understand all modifications<type>(<scope>): <subject>
<body>
feat: New featurefix: Bug fixrefactor: Code refactoring (no feature change, no bug fix)docs: Documentation changestest: Adding or updating testschore: Build, CI, dependency updatesperf: Performance improvementstyle: Code style changes (formatting, semicolons, etc.)