release

Agent Skills › phodal/routa › release

release

GitHub

自动化 Routa 版本发布流程，包括版本同步、发布说明及博客文章生成。支持干跑与正式发布，强调人工确认节点以确保安全。

.agents/skills/release/SKILL.md phodal/routa

Trigger Scenarios

用户请求发布新版本准备发布说明或生成博客文章执行版本同步和制品构建

Install

npx skills add phodal/routa --skill release -g -y

More Options

Non-standard path

npx skills add https://github.com/phodal/routa/tree/main/.agents/skills/release -g -y

Use without installing

npx skills use phodal/routa@release

指定 Agent (Claude Code)

npx skills add phodal/routa --skill release -a claude-code -g -y

安装 repo 全部 skill

npx skills add phodal/routa --all -g -y

预览 repo 内 skill

npx skills add phodal/routa --list

SKILL.md

Frontmatter

{
    "name": "release",
    "license": "MIT",
    "metadata": {
        "short-description": "Prepare Routa release artifacts and guide the final publish flow"
    },
    "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.",
    "allowed-tools": [
        "Bash",
        "Read",
        "Write"
    ],
    "compatibility": "Requires node, git, and optional ACP provider access for AI changelog summaries."
}

Prepare Routa releases with the existing repo scripts. Keep the workflow deterministic until human confirmation is needed for commit, tag, or push.

When to use

The user asks to release Routa, publish a version, prepare release notes, or generate a release blog post.
The task needs synchronized version bumps plus docs/releases/ artifacts.

Workflow

Confirm the target version and whether the user wants a dry run or an actual publish.
If a release summary already exists, pass it with --summary-file. If the user wants AI-generated summary copy, add --ai and optionally --ai-provider <name>.
Run the helper:

node scripts/release/prepare-release-artifacts.mjs <version>
node scripts/release/prepare-release-artifacts.mjs <version> --from <previous-tag> --ai --ai-provider claude

Review the generated files:
- docs/releases/v<version>-release-notes.md
- docs/releases/v<version>-changelog.md
- dist/release/changelog-summary-prompt.json
If the user only wants preparation, stop after review and validation.
If the user wants to publish, continue with either:

./scripts/release/publish.sh <version>

or the manual flow documented in docs/release-guide.md.

Guardrails

Do not tag or push without explicit user confirmation.
Do not discard unrelated worktree changes.
Prefer docs/releases/v<version>-release-notes.md as the blog/release-note source of truth after generation.
If git status --porcelain is not clean and the task is a real publish, call that out before invoking publish.sh.

References

Read references/release-workflow.md for the step-by-step release decision tree.
Read docs/release-guide.md when the task needs the full publish or verification checklist.