一键导入
release
// 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.
// 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.
| 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.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.
Use this skill for PDF generation, conversion, inspection, extraction, editing, form filling, OCR, redaction, or render comparison. Triggers include requests to create a PDF, convert Markdown or HTML or LaTeX or DOCX or PPTX to PDF, extract text or tables or images, fill or inspect forms, OCR scans, compare revisions, or redact content.
Use this skill as reference material when creating or editing presentation slide decks.
Use this skill for spreadsheet creation, editing, analysis, formatting, formula modeling, charting, or workbook review. Triggers include requests to create or modify an .xlsx file, build a model or tracker, format a workbook, add formulas or charts, or prepare a shareable spreadsheet deliverable.