菜单
Automate the Routa release preparation workflow from version sync through release note and blog generation. Use when the user wants to prepare, publish, or dry-run a Routa release.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/phodal/routa --skill release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Create or update a Routa Canvas artifact for the current task. Use when the user wants a live visual or interactive canvas generated from a Routa session.
Transforms rough requirements into well-structured GitHub issues. Use when the user provides a vague idea, feature request, or problem description and wants to create a GitHub issue. Analyzes codebase, explores solution approaches, researches relevant libraries, and generates actionable issues using `gh` CLI.
Use this skill for creating, editing, and reviewing DOCX files, including generation, formatting, content controls, tracked changes, comments, accessibility checks, redaction, rendering, and diff-based QA workflows.
基于 SOC 职业分类
正在显示 SKILL.md
| name | release |
| description | Automate the Routa release preparation workflow from version sync through release note and blog generation. Use when the user wants to prepare, publish, or dry-run a Routa release. |
| license | MIT |
| compatibility | Requires node, git, and optional ACP provider access for AI changelog summaries. |
| metadata | {"short-description":"Prepare Routa release artifacts and guide the final publish flow"} |
| allowed-tools | ["Bash","Read","Write"] |
Prepare Routa releases with the existing repo scripts. Keep the workflow deterministic until human confirmation is needed for commit, tag, or push.
docs/releases/ artifacts.--summary-file. If the user wants AI-generated summary copy, add --ai and optionally --ai-provider <name>.node scripts/release/prepare-release-artifacts.mjs <version>
node scripts/release/prepare-release-artifacts.mjs <version> --from <previous-tag> --ai --ai-provider claude
docs/releases/v<version>-release-notes.mddocs/releases/v<version>-changelog.mddist/release/changelog-summary-prompt.json./scripts/release/publish.sh <version>
or the manual flow documented in docs/release-guide.md.
docs/releases/v<version>-release-notes.md as the blog/release-note source of truth after generation.git status --porcelain is not clean and the task is a real publish, call that out before invoking publish.sh.references/release-workflow.md for the step-by-step release decision tree.docs/release-guide.md when the task needs the full publish or verification checklist.