菜单
Cut a Ralphy CLI release across GitHub Releases, Homebrew, and npm. Use when the user asks to release, tag, publish, or prepare release notes for the CLI. Public documentation and the marketing site live in sibling repositories and are synchronized separately when their content is affected.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/alecs5am/ralphy --skill dev-release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
How to make an analog-horror PSA short — the stenciled-pictogram / robo-broadcast / VHS-overlay format (faceless, 10 scenes × ~3s, 9:16, ~30s total). A domain overlay on the standard pipeline that supplies the IF / DO-NOT / BUT / AND scenario structure, the locked yellow-on-black 1970s-civil-defense pictogram visual STYLE, the chroma-key-to-alpha rule (icons must be transparent PNGs before composition), the robo-PSA voice profile (ElevenLabs "Alerter" community voice + ALL CAPS input + stability ~0.5 + style 0), the layered VHS-noise overlay stack (SnowCanvas + VcrTrackingCanvas + MobiusScanlines + MobiusWobble), the 5-layer RGB chromatic-split for icons + captions, the SMPTE colour-bars climax (3 wide vertical bars + filter blur(2.5px) mandatory), and the `-tune grain` CRF 30 final-encode rule for noise-heavy renders. Works for ANY PSA topic — "your fridge is not your fridge", "your phone is not your phone". USE WHEN the user asks for an analog horror PSA / "creepy PSA-style short" / fake-emergency-broadcast
Prompt and asset generation craft — turns an approved scenario into prompts.json and generated media through `ralphy generate`. Owns anchor order (location-master-plate first), character fit, photoreal-human prompting, model choice and cost preview, the reference-photo policy, regeneration rules, and the image/video quality gate. USE WHEN the user asks to "generate prompts", "generate assets", "make images / video / voiceover / music", "regenerate scene-XX", "try a different model", "A/B variant", "how much will this cost". TRIGGER (EN): "generate prompts", "make the images", "regenerate scene", "model swap", "cost preview", "A/B variant", "redo this shot".
Audio-first long-form explainer pipeline — takes one audio file (or a YouTube/podcast URL → audio) and produces a faceless overlay-driven video in the dev-essay / tech-podcast style (5-30 minutes, 16:9, no talking head). Orchestrates the existing `ralphy` primitives: yt-dlp pull → silence-remove → ElevenLabs Scribe v1 word-level transcript → Gemini audio-describe → LLM claim segmentation → per-claim overlay-type planner (code-block / terminal / tweet-card / browser-frame / screenshot / meme / diagram / quote-card / chapter-card / logo-pop) → asset prep (Playwright for screenshots, `ralphy generate image` for memes, ElevenLabs Music for the bed, ElevenLabs SFX for whoosh/pop/hit) → HyperFrames composition with chapter sub-compositions → `ralphy render`. USE WHEN the user drops an audio file (mp3 / wav / m4a) or a YouTube / podcast URL and asks for a long-form video edited on top, says "make a video from this audio / podcast", "monter ce podcast" (FR), "smontiruy podkast v video" (RU transliteration), "audio to
基于 SOC 职业分类
正在显示 SKILL.md
| name | dev-release |
| namespace | maintainer |
| description | Cut a Ralphy CLI release across GitHub Releases, Homebrew, and npm. Use when the user asks to release, tag, publish, or prepare release notes for the CLI. Public documentation and the marketing site live in sibling repositories and are synchronized separately when their content is affected. |
This skill ships the agent-facing CLI in this repository. It never releases the marketing site, public docs site, desktop app, or unattended farm runtime.
alecs5am/ralphy.../ralphy-docs, alecs5am/ralphy-docs.../ralphy-web, alecs5am/ralphy-web.../ralphy-desktop, alecs5am/ralphy-desktop.../ralphy-farm, alecs5am/ralphy-farm.Only the CLI repository receives the vX.Y.Z release tag. If a CLI change
affects public documentation, update and push ralphy-docs before tagging the
CLI. Web, desktop, and farm changes follow their own release processes.
One version must reach all three CLI channels:
SHA256SUMS.alecs5am/homebrew-tap formula.@alecs5am/ralphy on npm.Never amend or replace an existing release. Never publish only one channel.
Confirm the current branch is main, the worktree is clean, and gh auth status plus npm whoami identify the expected maintainer.
Read scripts/release/last-release-commit, the latest v* tag, and commits
since that baseline. Propose the semver bump and grouped release notes.
Inspect the diff for public-doc impact. If needed, update ../ralphy-docs,
validate docs.json, commit, and push that repository separately.
Run the CLI verification suite:
bun run lint
bun test --timeout 45000 tests/unit tests/integration
bun run build:bin:current
gitleaks detect --source .
After explicit user approval, update these version sources in lockstep:
package.jsoncli/lib/version.tsnpm/package.jsonAGENTS.mdCommit chore(release): vX.Y.Z, tag that commit vX.Y.Z, and push the
commit and tag. Do not create the GitHub Release manually; the release
workflow owns binaries, checksums, and the release object.
Watch the GitHub Actions release workflow to success.
Run scripts/release/update-brew-tap.sh vX.Y.Z and
scripts/release/publish-npm.sh X.Y.Z, then verify both registries resolve
the new version.
Update scripts/release/last-release-commit in a separate trailing commit
so the next release has an exact baseline.
Stop before tagging when tests fail, versions disagree, credentials are wrong,
there are no releasable commits, or the user has not approved the proposed
version. Documentation-only changes in ralphy-docs do not require a CLI tag.